Skip to content

Conversation

@smartiniOnGitHub
Copy link
Contributor

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

  • run npm run test and npm run benchmark
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message and code follows Code of conduct

@smartiniOnGitHub
Copy link
Contributor Author

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

@mcollina
Copy link
Member

Would you mind changing the yarn config for azure pipelines to require node >= 8.16.0?

node_8_x:
        node_version: >=8.16.0

@smartiniOnGitHub
Copy link
Contributor Author

smartiniOnGitHub commented Jun 21, 2019

@mcollina sure, I'll do that change, thanks for the suggestion.
Sorry another question, wouldn-t it be better to run Azure pipelines on Ubuntu-18.04 (LTS) instead of previous LTS (16.04) ? If yes I'll do even this change. Bye

@mcollina
Copy link
Member

Sorry another question, wouldn-t it be better to run Azure pipelines on Ubuntu-18.04 (LTS) instead of previous LTS (16.04) ? If yes I'll do even this change. Bye

Yes it would be! Would you mind sending a PR against master for that?

@smartiniOnGitHub
Copy link
Contributor Author

@mcollina sure, I'll raise another PR for that change (for master).

@smartiniOnGitHub
Copy link
Contributor Author

@mcollina all done, thanks again for all the help on this.
As always I made a lot of commits, hope PR merge with squash is good the same for you. Bye

Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

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

LGTM, good work!

@smartiniOnGitHub
Copy link
Contributor Author

all done, thanks to all for the help

@delvedor
Copy link
Member

Would you mind changing the yarn config for azure pipelines to require node >= 8.16.0?

@mcollina why?

@smartiniOnGitHub
Copy link
Contributor Author

in last commit/push all seems good in Azure, but 3 builds failed due to this error (strange):
"VS30063: You are not authorized to access https://tcmprodweu1.vstmr.visualstudio.com."
Could someone re-execute them, just to be sure that all is good the same ? Thanks a lot.

@mcollina
Copy link
Member

Would you mind changing the yarn config for azure pipelines to require node >= 8.16.0?

@mcollina why?

Our Azure Pipeline contact said so! ;).

@mcollina
Copy link
Member

@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
@smartiniOnGitHub
Copy link
Contributor Author

@mcollina yes, retried now (after the squash) and all builds are successful now, thanks for the suggestion.

@Eomm Eomm added internals Change that won't impact the surface API. v3.x Issue or pr related to Fastify v3 labels Jun 26, 2019
Copy link
Member

@Eomm Eomm left a 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

@smartiniOnGitHub
Copy link
Contributor Author

I think a rebase of next on top of master would be good, but Lead Fastify developers can say more ...

@mcollina
Copy link
Member

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.

Copy link
Member

@delvedor delvedor left a 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.

Copy link
Member

@mcollina mcollina left a 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'
@smartiniOnGitHub
Copy link
Contributor Author

smartiniOnGitHub commented Jun 28, 2019

hooks-async.js

done, yes now it looks better (big test file shorter, and this with specific tests restored and updated)

@smartiniOnGitHub
Copy link
Contributor Author

@mcollina latest changes done (as per your request), hope all is good now. Bye

Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

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

LGTM

@mcollina
Copy link
Member

Great work Sandro!

Copy link
Member

@delvedor delvedor left a comment

Choose a reason for hiding this comment

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

LGTM

@mcollina mcollina merged commit d6b621d into fastify:next Jul 3, 2019
Eomm pushed a commit to Eomm/fastify that referenced this pull request Nov 24, 2019
* 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
@mcollina mcollina mentioned this pull request Nov 24, 2019
4 tasks
@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

internals Change that won't impact the surface API. v3.x Issue or pr related to Fastify v3

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants