build : add Node.js@19.7

[abenhamdine]

• Node.js 19.7.0 has been published on 21/02/2023, see https://github.com/nodejs/node/releases/tag/v19.7.0
• Node.js 18 is now 18.14.12, see https://github.com/nodejs/node/releases/tag/v18.14.2
• Node.js 16 is now 16.19.1, see https://github.com/nodejs/node/releases/tag/v16.19.1
• body-parser is updated to version 1.20.2, see https://github.com/expressjs/body-parser/releases/tag/1.20.2

for nodejs version available in Github Actions, see https://github.com/actions/node-versions/releases
nodejs versions available in appveyor are slightly different, see https://www.appveyor.com/docs/linux-images-software/#node-js

One test is failing on appveyor :

Node.js 19.0 has updated V8 version, which had changedJSON.parse error messages.

Relevant Node.js commit: nodejs/node@71c193e

Are any further works expected in this direction? @abenhamdine

Just in case, this is how I improved the test in my project to support Node 19, @abenhamdine :

expect.stringMatching(// the 2nd option is for Node 19/(UnexpectedendofJSONinput|UnterminatedstringinJSONatposition)/)

Just in case, this is how I improved the test in my project to support Node 19, @abenhamdine :

expect.stringMatching(// the 2nd option is for Node 19/(UnexpectedendofJSONinput|UnterminatedstringinJSONatposition)/)

Thx I will give a look when I have some time

So there was a change in v8 for how it returns json errors. I have a test change in body-parser to account for this, which is more than a test change. We'll need to wait for that to be finished and released in body-parser before we can then add node 19 to the build of express.

Perhaps then this pr can just be limited to node 18 to get it landed, otherwise just waiting for that dependency update is all the is needed.

Perhaps then this pr can just be limited to node 18 to get it landed, otherwise just waiting for that dependency update is all the is needed.

Ok I will open a separate PR for node 18.12 update and keep this one for node 19.

FI the node 19 error is fixed upstream in https://github.com/expressjs/body-parser/releases/tag/1.20.2

I have rebased the branch on top of master, and have updated nodejs versions with last 16 and 18 versions available in GH and appveyor.
However, nodejs 18 and 19 tests fail because of a change in npm "npm ERR! The shrinkwrap option is deprecated"

I will give a look.

nodejs 18 tests are passing again, but nodejs 19 tests are still blocked by the same error, even with body-parser 1.20.2 :

thank you!

[abenhamdine]

• Node.js 19.7.0 has been published on 21/02/2023, see https://github.com/nodejs/node/releases/tag/v19.7.0
• Node.js 18 is now 18.14.12, see https://github.com/nodejs/node/releases/tag/v18.14.2
• Node.js 16 is now 16.19.1, see https://github.com/nodejs/node/releases/tag/v16.19.1
• body-parser is updated to version 1.20.2, see https://github.com/expressjs/body-parser/releases/tag/1.20.2

for nodejs version available in Github Actions, see https://github.com/actions/node-versions/releases
nodejs versions available in appveyor are slightly different, see https://www.appveyor.com/docs/linux-images-software/#node-js

One test is failing on appveyor :

Node.js 19.0 has updated V8 version, which had changedJSON.parse error messages.

Relevant Node.js commit: nodejs/node@71c193e

Are any further works expected in this direction? @abenhamdine

Just in case, this is how I improved the test in my project to support Node 19, @abenhamdine :

expect.stringMatching(// the 2nd option is for Node 19/(UnexpectedendofJSONinput|UnterminatedstringinJSONatposition)/)

Just in case, this is how I improved the test in my project to support Node 19, @abenhamdine :

expect.stringMatching(// the 2nd option is for Node 19/(UnexpectedendofJSONinput|UnterminatedstringinJSONatposition)/)

Thx I will give a look when I have some time

So there was a change in v8 for how it returns json errors. I have a test change in body-parser to account for this, which is more than a test change. We'll need to wait for that to be finished and released in body-parser before we can then add node 19 to the build of express.

Perhaps then this pr can just be limited to node 18 to get it landed, otherwise just waiting for that dependency update is all the is needed.

Perhaps then this pr can just be limited to node 18 to get it landed, otherwise just waiting for that dependency update is all the is needed.

Ok I will open a separate PR for node 18.12 update and keep this one for node 19.

FI the node 19 error is fixed upstream in https://github.com/expressjs/body-parser/releases/tag/1.20.2

I have rebased the branch on top of master, and have updated nodejs versions with last 16 and 18 versions available in GH and appveyor.
However, nodejs 18 and 19 tests fail because of a change in npm "npm ERR! The shrinkwrap option is deprecated"

I will give a look.

nodejs 18 tests are passing again, but nodejs 19 tests are still blocked by the same error, even with body-parser 1.20.2 :

thank you!

[abenhamdine]

• Node.js 19.7.0 has been published on 21/02/2023, see https://github.com/nodejs/node/releases/tag/v19.7.0
• Node.js 18 is now 18.14.12, see https://github.com/nodejs/node/releases/tag/v18.14.2
• Node.js 16 is now 16.19.1, see https://github.com/nodejs/node/releases/tag/v16.19.1
• body-parser is updated to version 1.20.2, see https://github.com/expressjs/body-parser/releases/tag/1.20.2

for nodejs version available in Github Actions, see https://github.com/actions/node-versions/releases
nodejs versions available in appveyor are slightly different, see https://www.appveyor.com/docs/linux-images-software/#node-js

One test is failing on appveyor :

Node.js 19.0 has updated V8 version, which had changedJSON.parse error messages.

Relevant Node.js commit: nodejs/node@71c193e

Are any further works expected in this direction? @abenhamdine

Just in case, this is how I improved the test in my project to support Node 19, @abenhamdine :

expect.stringMatching(// the 2nd option is for Node 19/(UnexpectedendofJSONinput|UnterminatedstringinJSONatposition)/)

Just in case, this is how I improved the test in my project to support Node 19, @abenhamdine :

expect.stringMatching(// the 2nd option is for Node 19/(UnexpectedendofJSONinput|UnterminatedstringinJSONatposition)/)

Thx I will give a look when I have some time

So there was a change in v8 for how it returns json errors. I have a test change in body-parser to account for this, which is more than a test change. We'll need to wait for that to be finished and released in body-parser before we can then add node 19 to the build of express.

Perhaps then this pr can just be limited to node 18 to get it landed, otherwise just waiting for that dependency update is all the is needed.

Perhaps then this pr can just be limited to node 18 to get it landed, otherwise just waiting for that dependency update is all the is needed.

Ok I will open a separate PR for node 18.12 update and keep this one for node 19.

FI the node 19 error is fixed upstream in https://github.com/expressjs/body-parser/releases/tag/1.20.2

I have rebased the branch on top of master, and have updated nodejs versions with last 16 and 18 versions available in GH and appveyor.
However, nodejs 18 and 19 tests fail because of a change in npm "npm ERR! The shrinkwrap option is deprecated"

I will give a look.

nodejs 18 tests are passing again, but nodejs 19 tests are still blocked by the same error, even with body-parser 1.20.2 :

thank you!

[abenhamdine]

• Node.js 19.7.0 has been published on 21/02/2023, see https://github.com/nodejs/node/releases/tag/v19.7.0
• Node.js 18 is now 18.14.12, see https://github.com/nodejs/node/releases/tag/v18.14.2
• Node.js 16 is now 16.19.1, see https://github.com/nodejs/node/releases/tag/v16.19.1
• body-parser is updated to version 1.20.2, see https://github.com/expressjs/body-parser/releases/tag/1.20.2

for nodejs version available in Github Actions, see https://github.com/actions/node-versions/releases
nodejs versions available in appveyor are slightly different, see https://www.appveyor.com/docs/linux-images-software/#node-js

One test is failing on appveyor :

Node.js 19.0 has updated V8 version, which had changedJSON.parse error messages.

Relevant Node.js commit: nodejs/node@71c193e

Are any further works expected in this direction? @abenhamdine

Just in case, this is how I improved the test in my project to support Node 19, @abenhamdine :

expect.stringMatching(// the 2nd option is for Node 19/(UnexpectedendofJSONinput|UnterminatedstringinJSONatposition)/)

Just in case, this is how I improved the test in my project to support Node 19, @abenhamdine :

expect.stringMatching(// the 2nd option is for Node 19/(UnexpectedendofJSONinput|UnterminatedstringinJSONatposition)/)

Thx I will give a look when I have some time

So there was a change in v8 for how it returns json errors. I have a test change in body-parser to account for this, which is more than a test change. We'll need to wait for that to be finished and released in body-parser before we can then add node 19 to the build of express.

Perhaps then this pr can just be limited to node 18 to get it landed, otherwise just waiting for that dependency update is all the is needed.

Perhaps then this pr can just be limited to node 18 to get it landed, otherwise just waiting for that dependency update is all the is needed.

Ok I will open a separate PR for node 18.12 update and keep this one for node 19.

FI the node 19 error is fixed upstream in https://github.com/expressjs/body-parser/releases/tag/1.20.2

I have rebased the branch on top of master, and have updated nodejs versions with last 16 and 18 versions available in GH and appveyor.
However, nodejs 18 and 19 tests fail because of a change in npm "npm ERR! The shrinkwrap option is deprecated"

I will give a look.

nodejs 18 tests are passing again, but nodejs 19 tests are still blocked by the same error, even with body-parser 1.20.2 :

thank you!

[abenhamdine]

• Node.js 19.7.0 has been published on 21/02/2023, see https://github.com/nodejs/node/releases/tag/v19.7.0
• Node.js 18 is now 18.14.12, see https://github.com/nodejs/node/releases/tag/v18.14.2
• Node.js 16 is now 16.19.1, see https://github.com/nodejs/node/releases/tag/v16.19.1
• body-parser is updated to version 1.20.2, see https://github.com/expressjs/body-parser/releases/tag/1.20.2

for nodejs version available in Github Actions, see https://github.com/actions/node-versions/releases
nodejs versions available in appveyor are slightly different, see https://www.appveyor.com/docs/linux-images-software/#node-js

One test is failing on appveyor :

Node.js 19.0 has updated V8 version, which had changedJSON.parse error messages.

Relevant Node.js commit: nodejs/node@71c193e

Are any further works expected in this direction? @abenhamdine

Just in case, this is how I improved the test in my project to support Node 19, @abenhamdine :

expect.stringMatching(// the 2nd option is for Node 19/(UnexpectedendofJSONinput|UnterminatedstringinJSONatposition)/)

Just in case, this is how I improved the test in my project to support Node 19, @abenhamdine :

expect.stringMatching(// the 2nd option is for Node 19/(UnexpectedendofJSONinput|UnterminatedstringinJSONatposition)/)

Thx I will give a look when I have some time

So there was a change in v8 for how it returns json errors. I have a test change in body-parser to account for this, which is more than a test change. We'll need to wait for that to be finished and released in body-parser before we can then add node 19 to the build of express.

Perhaps then this pr can just be limited to node 18 to get it landed, otherwise just waiting for that dependency update is all the is needed.

Perhaps then this pr can just be limited to node 18 to get it landed, otherwise just waiting for that dependency update is all the is needed.

Ok I will open a separate PR for node 18.12 update and keep this one for node 19.

FI the node 19 error is fixed upstream in https://github.com/expressjs/body-parser/releases/tag/1.20.2

I have rebased the branch on top of master, and have updated nodejs versions with last 16 and 18 versions available in GH and appveyor.
However, nodejs 18 and 19 tests fail because of a change in npm "npm ERR! The shrinkwrap option is deprecated"

I will give a look.

nodejs 18 tests are passing again, but nodejs 19 tests are still blocked by the same error, even with body-parser 1.20.2 :

thank you!

[abenhamdine]

• Node.js 19.7.0 has been published on 21/02/2023, see https://github.com/nodejs/node/releases/tag/v19.7.0
• Node.js 18 is now 18.14.12, see https://github.com/nodejs/node/releases/tag/v18.14.2
• Node.js 16 is now 16.19.1, see https://github.com/nodejs/node/releases/tag/v16.19.1
• body-parser is updated to version 1.20.2, see https://github.com/expressjs/body-parser/releases/tag/1.20.2

for nodejs version available in Github Actions, see https://github.com/actions/node-versions/releases
nodejs versions available in appveyor are slightly different, see https://www.appveyor.com/docs/linux-images-software/#node-js

One test is failing on appveyor :

Node.js 19.0 has updated V8 version, which had changedJSON.parse error messages.

Relevant Node.js commit: nodejs/node@71c193e

Are any further works expected in this direction? @abenhamdine

Just in case, this is how I improved the test in my project to support Node 19, @abenhamdine :

expect.stringMatching(// the 2nd option is for Node 19/(UnexpectedendofJSONinput|UnterminatedstringinJSONatposition)/)

Just in case, this is how I improved the test in my project to support Node 19, @abenhamdine :

expect.stringMatching(// the 2nd option is for Node 19/(UnexpectedendofJSONinput|UnterminatedstringinJSONatposition)/)

Thx I will give a look when I have some time

So there was a change in v8 for how it returns json errors. I have a test change in body-parser to account for this, which is more than a test change. We'll need to wait for that to be finished and released in body-parser before we can then add node 19 to the build of express.

Perhaps then this pr can just be limited to node 18 to get it landed, otherwise just waiting for that dependency update is all the is needed.

Perhaps then this pr can just be limited to node 18 to get it landed, otherwise just waiting for that dependency update is all the is needed.

Ok I will open a separate PR for node 18.12 update and keep this one for node 19.

FI the node 19 error is fixed upstream in https://github.com/expressjs/body-parser/releases/tag/1.20.2

I have rebased the branch on top of master, and have updated nodejs versions with last 16 and 18 versions available in GH and appveyor.
However, nodejs 18 and 19 tests fail because of a change in npm "npm ERR! The shrinkwrap option is deprecated"

I will give a look.

nodejs 18 tests are passing again, but nodejs 19 tests are still blocked by the same error, even with body-parser 1.20.2 :

thank you!

[abenhamdine]

• Node.js 19.7.0 has been published on 21/02/2023, see https://github.com/nodejs/node/releases/tag/v19.7.0
• Node.js 18 is now 18.14.12, see https://github.com/nodejs/node/releases/tag/v18.14.2
• Node.js 16 is now 16.19.1, see https://github.com/nodejs/node/releases/tag/v16.19.1
• body-parser is updated to version 1.20.2, see https://github.com/expressjs/body-parser/releases/tag/1.20.2

for nodejs version available in Github Actions, see https://github.com/actions/node-versions/releases
nodejs versions available in appveyor are slightly different, see https://www.appveyor.com/docs/linux-images-software/#node-js

One test is failing on appveyor :

Node.js 19.0 has updated V8 version, which had changedJSON.parse error messages.

Relevant Node.js commit: nodejs/node@71c193e

Are any further works expected in this direction? @abenhamdine

Just in case, this is how I improved the test in my project to support Node 19, @abenhamdine :

expect.stringMatching(// the 2nd option is for Node 19/(UnexpectedendofJSONinput|UnterminatedstringinJSONatposition)/)

Just in case, this is how I improved the test in my project to support Node 19, @abenhamdine :

expect.stringMatching(// the 2nd option is for Node 19/(UnexpectedendofJSONinput|UnterminatedstringinJSONatposition)/)

Thx I will give a look when I have some time

So there was a change in v8 for how it returns json errors. I have a test change in body-parser to account for this, which is more than a test change. We'll need to wait for that to be finished and released in body-parser before we can then add node 19 to the build of express.

Perhaps then this pr can just be limited to node 18 to get it landed, otherwise just waiting for that dependency update is all the is needed.

Perhaps then this pr can just be limited to node 18 to get it landed, otherwise just waiting for that dependency update is all the is needed.

Ok I will open a separate PR for node 18.12 update and keep this one for node 19.

FI the node 19 error is fixed upstream in https://github.com/expressjs/body-parser/releases/tag/1.20.2

I have rebased the branch on top of master, and have updated nodejs versions with last 16 and 18 versions available in GH and appveyor.
However, nodejs 18 and 19 tests fail because of a change in npm "npm ERR! The shrinkwrap option is deprecated"

I will give a look.

nodejs 18 tests are passing again, but nodejs 19 tests are still blocked by the same error, even with body-parser 1.20.2 :

thank you!

[abenhamdine]

• Node.js 19.7.0 has been published on 21/02/2023, see https://github.com/nodejs/node/releases/tag/v19.7.0
• Node.js 18 is now 18.14.12, see https://github.com/nodejs/node/releases/tag/v18.14.2
• Node.js 16 is now 16.19.1, see https://github.com/nodejs/node/releases/tag/v16.19.1
• body-parser is updated to version 1.20.2, see https://github.com/expressjs/body-parser/releases/tag/1.20.2

for nodejs version available in Github Actions, see https://github.com/actions/node-versions/releases
nodejs versions available in appveyor are slightly different, see https://www.appveyor.com/docs/linux-images-software/#node-js

One test is failing on appveyor :

Node.js 19.0 has updated V8 version, which had changedJSON.parse error messages.

Relevant Node.js commit: nodejs/node@71c193e

Are any further works expected in this direction? @abenhamdine

Just in case, this is how I improved the test in my project to support Node 19, @abenhamdine :

expect.stringMatching(// the 2nd option is for Node 19/(UnexpectedendofJSONinput|UnterminatedstringinJSONatposition)/)

Just in case, this is how I improved the test in my project to support Node 19, @abenhamdine :

expect.stringMatching(// the 2nd option is for Node 19/(UnexpectedendofJSONinput|UnterminatedstringinJSONatposition)/)

Thx I will give a look when I have some time

So there was a change in v8 for how it returns json errors. I have a test change in body-parser to account for this, which is more than a test change. We'll need to wait for that to be finished and released in body-parser before we can then add node 19 to the build of express.

Perhaps then this pr can just be limited to node 18 to get it landed, otherwise just waiting for that dependency update is all the is needed.

Perhaps then this pr can just be limited to node 18 to get it landed, otherwise just waiting for that dependency update is all the is needed.

Ok I will open a separate PR for node 18.12 update and keep this one for node 19.

FI the node 19 error is fixed upstream in https://github.com/expressjs/body-parser/releases/tag/1.20.2

I have rebased the branch on top of master, and have updated nodejs versions with last 16 and 18 versions available in GH and appveyor.
However, nodejs 18 and 19 tests fail because of a change in npm "npm ERR! The shrinkwrap option is deprecated"

I will give a look.

nodejs 18 tests are passing again, but nodejs 19 tests are still blocked by the same error, even with body-parser 1.20.2 :

thank you!