Update Node version

[lucpotage]

Thanks for your great app. It's the only app that makes me feel I can develop on iPad.

Unfortunately, after initiating a project and fetch dependencies, I had an error related to Node version and was not able to continue.

It's currently 12.19 in Code app whereas the latest Node LTS is currently 16.14. Do you think you could keep the Node version up-to-date?

[luni-moon]

Refer to issue #328

[bummoblizard]

Hey. It's being worked on https://github.com/nodejs-mobile/nodejs-mobile. I'm pretty sure it's doable but I can't tell when it will be done.

[bummoblizard]

It has been updated to Node 16 in the latest commit.

[wtpalexander]

Great to see Node 16, thanks so much for this work! Any ideas when this might make it to the AppStore? TestFlight beta is full and had some trouble installing through Xcode with the group ID’s and so on.

[bummoblizard]

It should be available within this week.

[wtpalexander]

Awesome, looking forward to it! 😄

[luni-moon]

Thanks!

[wtpalexander]

Am currently trying out the new Node 16 runtime. Am trying to run npm install and looks like I’m not having any luck. I get two different outputs alternating between the two. The second looks promising but returns almost instantly with no apparent installation. Still on my quest to run Nuxt (built on Vue.js) on iPad!

Running with verbose login yields this:

Running on iPad Pro 3rd Gen, iPad OS 15.2.1

Any ideas @bummoblizard?

[wtpalexander]

Ok that's a shame: so there's a possibility that this is just genuinely impossible with the current state of mobile Node?

[bummoblizard]

I set up a Vue project a while ago that can be run on Code App: https://github.com/bummoblizard/vue-archive
Maybe that could be used as a starting point.

[wtpalexander]

Interestingly I get the same errors as I do with Nuxt when trying your Vue repo. Not sure what the difference could be? I wonder if the AppStore build could be our difference?

[bummoblizard]

Deleting package-lock.json worked for me. Npm seems to spawn a sub process when fixing the older version package-lcok.json.

npm i
npm run demo

If npm i failed with Program interrupted or silently, you might need to run it again.

[bummoblizard]

Node 16 also fixed an issue of webpack middleware where previously it cannot watch file changes and recompile accordingly.

In index.js, this can be omitted:

watchOptions: {
    ignored: /.*/
  }