Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

Fix test issue for Node 10 #64

Merged
merged 2 commits into from
Jun 22, 2018
Merged

Fix test issue for Node 10 #64

merged 2 commits into from
Jun 22, 2018

Conversation

calebeby
Copy link
Member

@calebeby calebeby commented Jun 22, 2018

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

git checkout master
npm i # (this will also run the tests)

The clean test will fail.

git checkout fix-node-10
npm i # (this will also run the tests)

The tests should pass

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
@calebeby calebeby changed the title Fix test issue Fix test issue for Node 10 Jun 22, 2018
@calebeby calebeby requested a review from a team June 22, 2018 18:56
@gerardo-rodriguez
Copy link
Member

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:

This PR closes #14 by...

Thank you! 😄

@gerardo-rodriguez
Copy link
Member

Closes #63

@calebeby Ha! Looks like you beat me to it. Thank you! 😉

@gerardo-rodriguez
Copy link
Member

@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:

Validation Steps

  1. Do a thing

  2. Do this next thing

  3. Confirm xyz

This will help me greatly as I switch between project contexts. 😅 Thank you! 😉

@calebeby
Copy link
Member Author

@gerardo-rodriguez Updated ✅

@gerardo-rodriguez
Copy link
Member

Updated

Thanks @calebeby!! Very much appreciated! 😄

I just checked out master but the install step is failing for me in the validation steps. 😕

$ npm i
npm WARN The package postcss-class-prefix is included as both a dev and production dependency.

npm ERR! Cannot read property '0' of undefined

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/Rodriguez/.npm/_logs/2018-06-22T19_35_22_338Z-debug.log

🙊

This seems like a different issue. @tylersticka @megnotarte @derekshirk Does this happen to anyone else? 🤔

@gerardo-rodriguez
Copy link
Member

npm WARN The package postcss-class-prefix is included as both a dev and production dependency.

@calebeby and I agreed to open a new PR (#65) to fix this.

@gerardo-rodriguez
Copy link
Member

@calebeby Both the master and the fix-node-10 branch clean tests pass for me.

$ node -v
v9.11.2

On master:

  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 fix-node-10 branch:

  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? 🤔

@calebeby
Copy link
Member Author

@gerardo-rodriguez for me, node 9 works, but node 10 is the one causing the issue. I am using node v10.5.0

Copy link
Member

@gerardo-rodriguez gerardo-rodriguez left a 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! 🚀

@calebeby calebeby merged commit b3aed48 into master Jun 22, 2018
@calebeby calebeby deleted the fix-node-10 branch June 22, 2018 21:26
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Tasks fail in Node 10.x
2 participants