Skip to content
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

chore!: Normalize repository, dropping node <10.13 support #16

Merged
merged 5 commits into from
Nov 21, 2021

Conversation

sttk
Copy link
Contributor

@sttk sttk commented Nov 7, 2021

This PR updates this project:

  • Updates dependency versions
  • Introduces GitHub Actions
  • Adds, changes and deletes some project files

I separated testing to npm test and npm run cover because one test case does not work on nyc.

Closes #15

@sttk sttk requested a review from phated November 7, 2021 07:34
@sttk sttk linked an issue Nov 7, 2021 that may be closed by this pull request
@sttk sttk force-pushed the chore-normalize-repository branch from 405da19 to 2a37966 Compare November 7, 2021 09:10
Copy link
Member

@phated phated left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for looking into this @sttk! I had a few things.

LICENSE Outdated Show resolved Hide resolved
package.json Outdated
Comment on lines 26 to 27
"test": "mocha --async-only",
"cover": "nyc --reporter=lcov --reporter=text-summary npm test",
"coveralls": "npm run cover && istanbul-coveralls",
"cover": "nyc mocha --async-only",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is wrong. We move the nyc into the "test" script, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it. I'll modify it.

package.json Outdated
"expect": "^27.3.1",
"mocha": "^8.4.0",
"nyc": "^15.1.0",
"v8flags": "^3.2.0"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We'll need to release this and update to the next major

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just released v8flags v4.0.0

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I got it.

test/index.js Outdated Show resolved Hide resolved
package.json Outdated
Comment on lines 28 to 29
"respawn": "node test/bin/respawner --harmony test",
"nospawn": "node test/bin/respawner test"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How are these used?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think they aren't used, too. I'll remove them.

sttk and others added 3 commits November 8, 2021 19:44
Co-authored-by: Blaine Bublitz <blaine.bublitz@gmail.com>
Co-authored-by: Blaine Bublitz <blaine.bublitz@gmail.com>
@sttk
Copy link
Contributor Author

sttk commented Nov 8, 2021

@phated After using v8flag v4 the tests failed, because flagged-respawn processes on the premise that the separator of v8 options in the cache file is underscore, but became dash by this change.

For compatibility of the cache file, shouldn't we keep this separator underscore?

And Node.js>=v10 also accepts both dash and underscore as v8 option's separator.

@sttk
Copy link
Contributor Author

sttk commented Nov 8, 2021

Sorry, we should use dash and underscore separately depending on CACHE_VERSION of v8flag cache file.
I'll change about this.

@phated
Copy link
Member

phated commented Nov 8, 2021

@sttk this will be a semver major version increase, so we can stop supporting the snake_case flags. Even though node still supports these flags, we only supported them because old versions of node did not support hyphens.

@sttk
Copy link
Contributor Author

sttk commented Nov 9, 2021

@phated I got it. I'll remove the codes which replace dashes in v8 flags to underscores.

@sttk
Copy link
Contributor Author

sttk commented Nov 17, 2021

@phated I've modified what you pointed out. Please review them.

Copy link
Member

@phated phated left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excellent work! Thanks @sttk 🎊

@phated phated merged commit cbd39e6 into gulpjs:master Nov 21, 2021
@github-actions github-actions bot mentioned this pull request Nov 21, 2021
@sttk sttk deleted the chore-normalize-repository branch November 22, 2021 05:02
@sttk
Copy link
Contributor Author

sttk commented Nov 22, 2021

@phated Thank you for merging!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Normalize repository, dropping node <10.13
2 participants