updated package.json and package-lock.json to still allow this template to work even when node >=18 is installed #4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Oct 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Incompatible with #5 and #6 (#5 and #6 are much less hacky though)
Added node 16.20.2 as a dependency. This is because @vue/cli-shared-utils 4.5.19 (dependency of the various @vue/cli dependencies) requires @achrinza/node-ipc 9.2.2, which won't work with anything newer than 17 - rendering this template unusable if you have node 18 (or later) installed on your system (unless you faff around with a node version manager).
Opted to depend on the latest version of node 16 instead of 17 because 16 was an LTS - therefore probably safer to use I guess (although it's still EOL).
Also updated the lockfile as well, to make it even easier to get up and running for the end user.
This is an incredibly hacky workaround - but it looks like the only other option would be to do a lot of faffing around with all the dependencies allowing the vue cli utils to be updated (in turn using a node-ipc version that works on node >=18) - or just migrate from vue cli to Vite - or maybe go all-in and migrate the project from Vue 2 to Vue 3. However, I have 0 prior experience with Vue (or understanding of how any of this works), so chances are that any attempts I may make at migrating it would end very badly. So, in the meantime, I'll just contribute this workaround.