-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm start fails on windows #108
Comments
@manucorporat I think this issue is for you. I have investigated the problem, and it seems that on Windows the Optimizer is bypassed. Not sure as to why but the generated code is the original code without code splitting. Something about Windows file-paths (my guess) must be confusing the optimizer in a way that is preventing it from doing its job. The failure mode is that the code generated on windows is similar too: const MyCmp = qComponent({
onRender: qHook(() => <span>ABC</span>)
}) Whereas the correct code should be: const MyCmp = qComponent({
onRender: qHook('./path#symbol')
}) PS: I have created a better error msg for this condition: #127 |
If I understand the correct result, transforming by the executable |
Hi All,
I tried
npm init qwik@latest
on a windows 10 machineChose the starter, did
cd qwik-app
npm install
Did
npm start
, all good so far,Tried to go to
http://localhost:8080
in a browser, this fails, and outputs this in the consolenode is version 16.13.1
Am I missing a step? Perhaps windows isn't supported?
The text was updated successfully, but these errors were encountered: