-
Notifications
You must be signed in to change notification settings - Fork 67
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
Nanogen -w doesn't work on windows #10
Comments
Hi! I can confirm the issue and will investigate. Thanks for reporting! |
Any progress on this one? Thanks in advance! |
+1 |
Hi, (Win7) I made some edits to the files (this is bad practice, but I needed it): The problem with "operation not permitted" in /lib/modules/build.js -> fse.copySync(). Didn't dig deep ... Just used: await fse.copy() const build = async (options = {}) => { Changes in /lib/modules/serve.js: ... /**
Changes in /lib/utils/server.js: Added to parameters: noCssInject: true. Без этого параметра перезагрузка работала через раз. Without this parameter, the restart worked terribly. It is better not to use it in your project. This is a one-time solution. Perhaps it will help solve the problem. |
Thanks, @a3con! It will surely help solving the issue. |
I add a
"watchmode": "nanogen -w"
script topackage.lock
When I write
npm run watchmode
in windows console it gives me next error:I have /jsons folder in /assets. Normally with
nanogen
it's added to /publicBut /public directory is empty at all. What is the reason?
UPD2 found a solution from this user: run command prompt in administrator mode.
nanogen -w
starts a server but after any changes it crashes with the same error.The text was updated successfully, but these errors were encountered: