Bump nuxt version #2524
Closed
Bump nuxt version #2524
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
|
What version of node are you using? I'm still on v16.14.0 and think that may need to be updated first. I planned to jump to node 20 |
|
Oh, my bad. I'm in Node 18, I was on Node 16, but a few weeks ago, I updated it to 18 because 16 reached its end of life. Also, I ran some tests with Node 20, and it's still working well (but I don't try to use it deeply) |
|
There was a bunch more stuff I had to do to bump to node 20. I did that all here 7f35027 so you should be good now if you pull and switch to node 20. |
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.
I create this pull request to update the Nuxt version in the AudioBookShelf repo from v2.15.8 to v2.17.3.
When I tried setting up my environment locally and ran npm run in the client folder, I hit an error:
To fix this I need to put some code on package.json
It looks like there's a bug related to the crypto node library. Nuxt fixed this in version v2.16.2, but AudioBookShelf is currently on v2.15.8. So, I decided to jump to the latest, v2.17.3.
I dug into the Breaking Changes between v2.15.8 and v2.17.3. The only one I found was in the upgrade to 2.16.0, which was about a new postcss options format. You can get all the details here.
After updating the nuxt.config.js file, I tested the app locally. Everything seemed fine - no errors while navigating pages, and both npm run build and npm run generate worked without a hitch.