starred/audiobookshelf
1
0
Fork 0
mirror of https://github.com/advplyr/audiobookshelf.git synced 2026-05-30 23:40:40 +02:00
Code Issues 1.0k Packages Projects Releases 10 Wiki Activity

[PR #2524] [CLOSED] Bump nuxt version #3735

New Issue
Closed
opened 2026-04-25 00:16:51 +02:00 by adam · 0 comments
adam commented 2026-04-25 00:16:51 +02:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/advplyr/audiobookshelf/pull/2524
Author: @apiweb
Created: 1/18/2024
Status: ❌ Closed

Base: master ← Head: bumpNuxt

📝 Commits (1)

📊 Changes

3 files changed (+13649 additions, -13554 deletions)

View changed files

📝 client/nuxt.config.js (+1 -1)
📝 client/package-lock.json (+13646 -13551)
📝 client/package.json (+2 -2)

📄 Description

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:

Screenshot 2024-01-18 at 08 57 04

To fix this I need to put some code on package.json

Screenshot 2024-01-18 at 08 55 27

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.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/advplyr/audiobookshelf/pull/2524 **Author:** [@apiweb](https://github.com/apiweb) **Created:** 1/18/2024 **Status:** ❌ Closed **Base:** `master` ← **Head:** `bumpNuxt` --- ### 📝 Commits (1) - [`ef1b511`](https://github.com/advplyr/audiobookshelf/commit/ef1b5110089df4e40b4fced08b1fbc4b8ec222c6) Bump nuxt version ### 📊 Changes **3 files changed** (+13649 additions, -13554 deletions) <details> <summary>View changed files</summary> 📝 `client/nuxt.config.js` (+1 -1) 📝 `client/package-lock.json` (+13646 -13551) 📝 `client/package.json` (+2 -2) </details> ### 📄 Description I create this pull request to update the Nuxt version in the AudioBookShelf repo from [v2.15.8](https://github.com/nuxt/nuxt/releases/tag/v2.15.8) to [v2.17.3](https://github.com/nuxt/nuxt/releases/tag/v2.17.3). When I tried setting up my environment locally and ran npm run in the client folder, I hit an error: ![Screenshot 2024-01-18 at 08 57 04](https://github.com/advplyr/audiobookshelf/assets/5881027/f1d12f33-09c8-4211-9a9b-777b36bf7a85) To fix this I need to put some code on package.json <img width="1387" alt="Screenshot 2024-01-18 at 08 55 27" src="https://github.com/advplyr/audiobookshelf/assets/5881027/aec78cc9-7b68-4a04-ba41-e6831599141c"> It looks like there's a bug related to the crypto node library. Nuxt fixed this in version [v2.16.2](https://github.com/nuxt/nuxt/releases/tag/v2.16.2), but AudioBookShelf is currently on [v2.15.8](https://github.com/nuxt/nuxt/releases/tag/v2.15.8). So, I decided to jump to the latest, [v2.17.3](https://github.com/nuxt/nuxt/releases). I dug into the Breaking Changes between [v2.15.8](https://github.com/nuxt/nuxt/releases/tag/v2.15.8) and [v2.17.3](https://github.com/nuxt/nuxt/releases). 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](https://github.com/nuxt/nuxt/pull/9671). 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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2026-04-25 00:16:51 +02:00
adam closed this issue 2026-04-25 00:16:51 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
authentication
backlog
bug
chapter editor
config-issue
ebooks
encoding/embedding
enhancement
help wanted
listening sessions & progress
planned
possible plugin
progress sync
pull-request
Mirrored from GitHub Pull Request
 sorting/filtering/searching
unable to reproduce
upload
users & permissions
waiting
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#3735
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?