-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Drop nodejs 6 for next (Fastify 3) #1713
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
Drop nodejs 6 for next (Fastify 3) #1713
Conversation
|
Hi all, note that I put here some TODO because not sure you prefer that I update code here (I think it's good to do here), just for a check ... tell me so during next days I can finish these changes and then continue with the other issue related to other code changes. Thanks. Bye |
|
Would you mind changing the yarn config for azure pipelines to require node >= 8.16.0? |
|
@mcollina sure, I'll do that change, thanks for the suggestion. |
Yes it would be! Would you mind sending a PR against master for that? |
|
@mcollina sure, I'll raise another PR for that change (for master). |
|
@mcollina all done, thanks again for all the help on this. |
mcollina
left a comment
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.
LGTM, good work!
|
all done, thanks to all for the help |
@mcollina why? |
|
in last commit/push all seems good in Azure, but 3 builds failed due to this error (strange): |
Our Azure Pipeline contact said so! ;). |
|
@delvedor can you LGTM this? @smartiniOnGitHub would you mind squashing your commits to retrigger CI, I think the failure should go away (and it's not related anyway). |
add TODO for code updates/cleanup (check if do here or if in the other issue/PR) Update README.md Co-Authored-By: Matteo Collina <matteo.collina@gmail.com> Update docs/Benchmarking.md Co-Authored-By: Matteo Collina <matteo.collina@gmail.com> Update package.json Co-Authored-By: Matteo Collina <matteo.collina@gmail.com> revert version update getHeader to use hasHeader (available since Node.js 7.7.x) and remove fallback implementation try yarn builds for Node.js 8 aligned with requirements in 'package.json', to check if it works with version range align even npm azure pipelines to those of yarn (Node.js 8.x requirements) update code to Node.js 8 as minimum version (remove TODO etc) update code to Node.js 8 as minimum version (remove TODO etc) update code to Node.js 8 as minimum version (remove TODO etc) move getHeader implementation directly in Reply.prototype.getHeader drop Node.js 11 from doc and from CI on Azure (yarn and npm) (try to) simplify info on HTTP2 support CI on Azure, specify version range in a way more aligned to npm syntax
|
@mcollina yes, retried now (after the squash) and all builds are successful now, thanks for the suggestion. |
Eomm
left a comment
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.
A question in my mind since this PR is the first (ready to merge) big split from v2:
which is the right process to keep the next branch aligned with the features added in v2/master?
Opening a PR from master to next or rebasing periodically?
Because the next branch starts in between v2.3/2.4
|
I think a rebase of next on top of master would be good, but Lead Fastify developers can say more ... |
That'd be ok. it's not urgent anyway. |
delvedor
left a comment
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.
I think we should keep the async hook test in its own file.
Currently, the hooks test file is about 3000+ lines long.
mcollina
left a comment
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.
Some nits.
Also, would you mind restoring test/hooks-async.js and rename it to test/hooks-async.test.js and make that runnable?
…ike others; remove its tests from 'hooks.test.js'
done, yes now it looks better (big test file shorter, and this with specific tests restored and updated) |
|
@mcollina latest changes done (as per your request), hope all is good now. Bye |
mcollina
left a comment
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.
LGTM
|
Great work Sandro! |
delvedor
left a comment
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.
LGTM
* update requirements to Node.js 8 LTS or later; update docs add TODO for code updates/cleanup (check if do here or if in the other issue/PR) Update README.md Co-Authored-By: Matteo Collina <matteo.collina@gmail.com> Update docs/Benchmarking.md Co-Authored-By: Matteo Collina <matteo.collina@gmail.com> Update package.json Co-Authored-By: Matteo Collina <matteo.collina@gmail.com> revert version update getHeader to use hasHeader (available since Node.js 7.7.x) and remove fallback implementation try yarn builds for Node.js 8 aligned with requirements in 'package.json', to check if it works with version range align even npm azure pipelines to those of yarn (Node.js 8.x requirements) update code to Node.js 8 as minimum version (remove TODO etc) update code to Node.js 8 as minimum version (remove TODO etc) update code to Node.js 8 as minimum version (remove TODO etc) move getHeader implementation directly in Reply.prototype.getHeader drop Node.js 11 from doc and from CI on Azure (yarn and npm) (try to) simplify info on HTTP2 support CI on Azure, specify version range in a way more aligned to npm syntax * restore 'hooks-async.js' and set the '.test.js' extension to run it like others; remove its tests from 'hooks.test.js' * remove direct reference to main fastify source from https tests, not really needed
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Hi all,
this is mainly an update/cleanup on documentation (and CI tools) for removing Node.js support in Fastify v3 (in its dev branch 'next'), related to the issue#1647 . With this, minimum Node.js version set is 8 LTS (8.9.0).
Checklist
npm run testandnpm run benchmark