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

[DO NOT MERGE] feat: run node 16 on device #1104

Draft
wants to merge 10 commits into
base: develop
Choose a base branch
from

Conversation

achou11
Copy link
Member

@achou11 achou11 commented Jun 1, 2023

Closes #1100

Notes:

@achou11 achou11 changed the title WIP: fix: run node 16 on device WIP: feat: run node 16 on device Jun 5, 2023
@achou11 achou11 changed the title WIP: feat: run node 16 on device feat: run node 16 on device Jun 12, 2023
@achou11 achou11 requested review from gmaclennan and ErikSin and removed request for gmaclennan June 12, 2023 17:29
@achou11 achou11 marked this pull request as ready for review June 12, 2023 18:21
@achou11
Copy link
Member Author

achou11 commented Jun 14, 2023

looks like backend tests are failing due to upgrading Node version from 12 to 16. seems to be related to different streams behavior.

  1. for one of the beforeAfterStream tests, this test is failing:

test("bubble errors from write()", function (t) {

seems like the main reason is the result of this line:

const ok = wrappedStream.write(chunk);

In node 12, ok is true but in node 16, ok is false. seems like 16 actually has the behavior I would expect for this test's case.


  1. a couple of the upgrade-storage tests are failing:

test("createWriteStream() --> invalid hash = installer does not appear as option", async t => {

test("Trying to write an invalid APK throws an error (and doesn't leave any files around)", async t => {

I'm noticing that this listener in beforeAfterStream is not being triggered as expected in node 16, causing the tests to fail I guess:

wrappedStream.once("error", e => {


In both cases, I'm able to add a couple of lines to fix them, but they're very uninformed and while all of the backend tests pass as a result (locally), I still lack confidence.

Created a branch with these "fixes": 1100/upgrade-nodejs-mobile-rn...ac/node-16-upgrade-backend-tests

cc @gmaclennan

@achou11 achou11 changed the title feat: run node 16 on device [DO NOT MERGE] feat: run node 16 on device Jun 15, 2023
@achou11
Copy link
Member Author

achou11 commented Jun 15, 2023

not going to merge this but keeping it as a draft for the foreseeable future. refer to #1100 (comment) for more details

@achou11 achou11 marked this pull request as draft June 15, 2023 18:13
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.

upgrade nodejs-mobile-react-native to v16.17.10
1 participant