#Qwik starter app errors

91 messages · Page 1 of 1 (latest)

valid moat
#

I'm fairly new to qwik, and trying to get into it. So I started the qwik CLI and followed the steps, chose Basic app with routing (the recommended one), chose to initialize a git repository and install dependencies. And after running npm start I get presented with the error that router outlet is not found. Now, considering it happened after I just created the starter app I figured it might have been corrupted so I reinstalled and restarted it, yet it's still happening and that just breaks the entire app. Did I do something wrong or did this version somehow got something messed up?

image.png
valid moat
#

Anyone? Please?

valid moat
#

Please?

loud phoenix
#

I mean the starter should work, right? So maybe there's a bug that's been introduced recently.

What version of Qwik and Qwik City? Did you install with @latest? npm create qwik@latest I think is the command.

#

I would say let's see if we can get more info about your errors and then we can ping someone from the team on Discord.

You said you tried doing a second install, did you delete everything and start completely fresh? I would try that, and worst case you could try stepping back a version or two and see if that works.

If it's a bug it must've been introduced very recently because I started a qwik project a week or so ago without issue, so might need to step back 7-14 days and pick a version released in that time frame. Looks like we have 0.102 2 weeks ago and 0.101 3 weeks ago.

valid moat
#

I did it just like that

#

npm create qwik@latest, chose basic app, installed dependencies, initialized git

#

Did npm start

#

And I get presented with that

#

And then all the scripts in the starter app break

valid moat
#

Just did npm create all over and scrapped the previous

cyan sage
#

perhaps the dependency aren't installing with the create qwik. Maybe try deleting node_modules and then npm install manually.

valid moat
#

I mean, it would just completely regenerate it

cyan sage
#

I'm not sure what you mean by clean reinstall. I'm suggest that perhaps the script isn't working right at the stage where installs the packages.

#

I've done lots of create qwik and haven't had issues in a very long time. Just trying to think of things that might help.

#

Maybe try disabling any browser extensions?

valid moat
valid moat
#

So it's a complete reinstall of everyrhing

valid moat
green stag
#

Which node and npm versions are you using?

valid moat
#

Node v20, npm v9.6.5

#

I tried asking some people in the qwik team but they've been pretty unhelpful (which is a bit sad to see but unfortunately it's a bit of a common occurrence, still disappointing though in my opinion)

green stag
#

I understand, give me a minute to confirm my versions. Just did a fresh install today and it worked fine

#

Am currently on node v18.12.1. I believe the issue you are facing is due to using the current version which is unstable

#

You'll need to install the latest LTS version of node which is v18. 16

valid moat
#

Ah

#

Wait let me see with the LTS version

#

If this is really the issue

#

Then

#

That would be sad

green stag
#

Let me know how it goes

valid moat
#

Will do, just give me 10 years because my PC takes forever to uninstall apps

green stag
#

No worries. Will check in later

valid moat
#

And now for the big test

#

Update: Router outlet still broken

#

And it isn't an extension issue because I don't have any + tried getting one and disabling

green stag
#

That's unfortunate

#

Which command are you using to launch the app?

valid moat
#

npm start

#

As shown in the docs

#

Followed it to a T

#

Didn't even add anything yet

green stag
#

That's strange

#

Are you on Windows, Linux or Mac?

valid moat
#

Windows

green stag
#

Cool, am also on Windows

valid moat
#

All the stranger

green stag
#

The other culprit I can think of is your hard drive

valid moat
#

What may be wrong with it

green stag
#

You mentioned it takes ages to install new packages, right

valid moat
#

Not packages, apps

#

My PC just sucks honestly lol

#

The uninstaller takes forever

#

But I doubt that's the issue

#

It was working like a month and a half ago when I was just messing around with it but now I'm starting to create something with it and it just breaks

green stag
#

Do you use nvm to manage node.js?

valid moat
#

No

#

I don't use any nodejs manager

#

Only use the node package manager

valid moat
loud phoenix
#

Nvm is not necessary but allows you to have multiple node versions and switch easily. It comes in handy sometimes.

I would delete your qwik app and create it again fresh, just to try. Or let us know if you figured it out!

loud phoenix
#

Was this solved? I was successfully able to create starters with npm, yarn, and pnpm, but with both yarn and pnpm I had to manually install the modules after the CLI completed. BTW, my node.js version is 16.16.0 and npm v8.11.0.

valid moat
#

It still errors

#

And I did create it from scratch

#

Way too many times

loud phoenix
#

I'm not sure what else to try, other than trying the node/npm versions I'm currently using. Node v 16.16.0 & npm v 8.11.0. (And that's when NVM could come in handy - make it a lot easier to switch node/npm versions!) And make sure you npm i just in case it failed to do so automatically during initialization (although I did not need to when using NPM). Any way to reproduce this issue in a stackblitz or on another computer?

valid moat
#

Then retried on my PC and it won't work

#

I tried installing manually

#

It was all up to date it said

#

Tried different versions as well

primal pagoda
# valid moat I tried asking some people in the qwik team but they've been pretty unhelpful (w...

We talked about it privately, I just wanted to write here so others who read it will see our response to the quoted message - the team is super busy, so DMs are not an effective way to get answers, it's better to open up a github issue with a reproduction or rely on the friendly community members here in discord or on the other social groups.

Two of our community values are friendliness and being patient - that means - if someone helps us publicly, let's thank them publicly and appreciate their time. If someone doesn't respond to us fast enough or can't help us, let's keep in mind they don't owe us anything, and if they help us it's out of pure goodwill. This is FREE open source and is true for any framework / library.

If we keep that in mind, we'll scale better as a community and stay friendly and supportive.

#

Now on to a possible solution:

Maybe it's a firewall issue or browser extension

I would install nvm and install a different node version and allow node to operate when the firewall pops up

valid moat
#

No browser extensions as I said, firewall doesn't seem to interfere either

primal pagoda
#

Have you tried what I suggested with nvm?

valid moat
#

I tried changing versions, yea

primal pagoda
#

I run on a windows machine and don't experience these issues, so it must be a specific configuration for this specific windows, either firewall blocking this port, specific browser or something else, it's hard to tell and to find.

Let us know if you find out what it was

valid moat
#

It's the exact same configuration from a month ago when the starter worked

#

Now it just doesn't

primal pagoda
#

OK, when you figure it out, we'd love to know what on your machine caused it not to work

valid moat
#

So is there no way to identify it? Am I supposed to find it out on my own?

primal pagoda
#

If you can't reproduce it on stackblitz / other machines, and tried everything suggested, I think we are out of ideas for now, so try it on a different computer, or a fresh install on a virtual machine, and if it works, see which programs / configuration might cause these 404s

valid moat
#

Alright, well, thanks

#

I guess this post can be closed now