-
Notifications
You must be signed in to change notification settings - Fork 14
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
Miscellaneous fixes and updates #7
Conversation
and do not keep it under version control
Also, upgrade all dependencies to latest versions
@tripu, can you explain these changes a bit?
(The newbie mistakes with npm and node.js) |
@iherman, sure, I'll try:
Yes, it can. Those package names I removed from
|
O.k. What led me on the wrong path is looking at the
Giving some second thoughts I think I would prefer to stay with Node 6. On the node.js site the download of Node 6 is still presented as "Recommended for most users" which I translate that Node 8 is still a bit experimental. Which also means that others who may want to download this script for local use (and I hope some people in the WG do that) may have only Node 6 installed on their local machine. |
Okay. You can still test with both and try to maintain compatibility.
Yes, it's still four months until version 8 becomes LTS. |
…some of them to adopt Node.js & npm's common/best practices.
node_modules/
directory and do not keep it under version control.package.json
:package-lock.json
(older versions of Node.js will ignore it).