-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
node 18 support #7116
Comments
got the same issue when trying to install: yarn global add @vue/cli@next |
Im getting an issue with
|
I think requiring |
The temporary solution is: yarn --ignore-engines Reference: $ yarn help | grep -- --ignore
--ignore-engines ignore engines check
--ignore-optional ignore optional dependencies
--ignore-platform ignore platform checks
--ignore-scripts don't run lifecycle scripts |
How do I even create a project with vue-cli? It seems to run yarn automatically |
yarn config set ignore-engines true |
Ok thanks! Do you know if there a permanent solution in the works? Considering this breaks new installs it seems weird it isnt a higher priority. Also I don't like setting to ignore other things as there may be other conflicts etc. |
I admit, I am wondering too that this topic does not get much more attention. But perhaps Node.js 18 does not have too much adoption yet? But I hardly believe that... |
Please update the dependency to @achrinza/node-ipc@9.2.4 |
I'm wrong. The reason the version is pinned should be obvious after the fiasco that made a switch to a fork necessary. We'll see to it that this is upgraded. Npm also supports overrides for some time now: https://docs.npmjs.com/cli/v8/configuring-npm/package-json#overrides |
Fixed in 5.0.6 |
saved my life. |
* Setting 'ignore-engines=true' prior to invoking vue create. This fixed a problem with some package not ready to deal with the latest version of node. (vuejs/vue-cli#7116)
--ignore-engines vuejs/vue-cli#7116
test('top level test', async (t) => { await t.test('subtest 2', (t) => { |
Now it's the same with node 20 - please support this version |
This started with an attempt to upgrade Astro to v3.0 - Astro v3.0 no longer supports Node 16. We need to upgrade our tooling to Node 18. See https://docs.astro.build/en/guides/upgrade-to/v3/#removed-support-for-node-16 - vue-cli contains a dependency that is not compatible with Node 18 (@achrinza/node-ipc@9). See vuejs/vue-cli#7116 This compatible issue has been fixed but Centrapay Docs does not need vue-cli and the module itself is in maintenance mode. See https://cli.vuejs.org/ Removing these vue-cli dependencies required a change to use eslint directly for linting instead. We are now using eslint-plugin-vue (it was already installed) as per Vue's official guidelines. See https://vuejs.org/guide/scaling-up/tooling.html#linting Test plan: - Confirm Eslint is linting Vue files using its --debug flag - Confirm that the local dev server runs correctly - Confirm that the static Centrapay Docs site builds correctly - Confirm the site navigation still works
This started with an attempt to upgrade Astro to v3.0 - Astro v3.0 no longer supports Node 16. We need to upgrade our tooling to Node 18. See https://docs.astro.build/en/guides/upgrade-to/v3/#removed-support-for-node-16 - vue-cli contains a dependency that is not compatible with Node 18 (@achrinza/node-ipc@9). See vuejs/vue-cli#7116 This compatible issue has been fixed but Centrapay Docs does not need vue-cli and the module itself is in maintenance mode. See https://cli.vuejs.org/ Removing these vue-cli dependencies required a change to use eslint directly for linting instead. We are now using eslint-plugin-vue (it was already installed) as per Vue's official guidelines. See https://vuejs.org/guide/scaling-up/tooling.html#linting I've also added init: true to the docker compose config to forward signals correctly. Test plan: - Confirm Eslint is linting Vue files using its --debug flag - Confirm that the local dev server runs correctly - Confirm that the static Centrapay Docs site builds correctly - Confirm the site navigation still works
This started with an attempt to upgrade Astro to v3.0 - Astro v3.0 no longer supports Node 16. We need to upgrade our tooling to Node 18. See https://docs.astro.build/en/guides/upgrade-to/v3/#removed-support-for-node-16 - vue-cli contains a dependency that is not compatible with Node 18 (@achrinza/node-ipc@9). See vuejs/vue-cli#7116 This compatible issue has been fixed but Centrapay Docs does not need vue-cli and the module itself is in maintenance mode. See https://cli.vuejs.org/ Removing these vue-cli dependencies required a change to use eslint directly for linting instead. We are now using eslint-plugin-vue (it was already installed) as per Vue's official guidelines. See https://vuejs.org/guide/scaling-up/tooling.html#linting I've also added init: true to the docker compose config to forward signals correctly. See our dev environment for a live preview - http://centrapay-docs.dev.s3-website-ap-southeast-1.amazonaws.com Test plan: - Confirm Eslint is linting Vue files using its --debug flag - Confirm that the local dev server runs correctly - Confirm that the static Centrapay Docs site builds correctly - Confirm the site navigation still works
What problem does this feature solve?
It solve the issue that vue cli can't be installed on node 18 because
@achrinza/node-ipc@9
doesn't support itWhat does the proposed API look like?
Allow
@achrinza/node-ipc@10
The text was updated successfully, but these errors were encountered: