-
Notifications
You must be signed in to change notification settings - Fork 0
Conversation
Solved with rm package-lock.json; npm i That's sad :( nodejs/node#20281 Was running into this issue, but it was solved after resetting lockfile
Thanks @calebeby! May I offer a friendly suggestion? :) To help understand which specific GH issue this PR closes, could you use a GH "close" keyword as part of your summary/description? Something like:
Thank you! 😄 |
@calebeby One more suggestion, if I may. :) We started doing this in another project, but could you provide some steps to validate the fix? Something like:
This will help me greatly as I switch between project contexts. 😅 Thank you! 😉 |
@gerardo-rodriguez Updated ✅ |
Thanks @calebeby!! Very much appreciated! 😄 I just checked out
🙊 This seems like a different issue. @tylersticka @megnotarte @derekshirk Does this happen to anyone else? 🤔 |
@calebeby Both the $ node -v
v9.11.2 On clean task
✔ Cleans up files and folders
copy task
✔ Copies asset files
css task
✔ Processes CSS files
html task
✔ Compiles Handlebars templates
js task
✔ Transpiles and resolves dependencies
total: 5
passing: 5
duration: 8s On the clean task
✔ Cleans up files and folders
copy task
✔ Copies asset files
css task
✔ Processes CSS files
html task
✔ Compiles Handlebars templates
js task
✔ Transpiles and resolves dependencies
total: 5
passing: 5
duration: 9.3s Should I be testing on a different node version? 🤔 |
@gerardo-rodriguez for me, node 9 works, but node 10 is the one causing the issue. I am using node |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works like a charm! 🚀
This PR closes #63
The tests were not passing because this issue was showing up: nodejs/node#20281
For some reason it was solved by regenerating the lockfile (the bug must have been fixed in a minor version bump of a dependency)
Validation Steps
The
clean
test will fail.The tests should pass