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 #4430] [MERGED] Add ENV REACT_CLIENT_PATH to target a Nextjs frontend instead of Nuxt #4248

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

📋 Pull Request Information

Original PR: https://github.com/advplyr/audiobookshelf/pull/4430
Author: @advplyr
Created: 6/24/2025
Status: ✅ Merged
Merged: 6/24/2025
Merged by: @advplyr

Base: master ← Head: experimental_next_client

📝 Commits (1)

  • a992400 Add ENV REACT_CLIENT_PATH to target a Nextjs frontend instead of Nuxt

📊 Changes

3 files changed (+57 additions, -31 deletions)

View changed files

📝 index.js (+1 -0)
📝 server/Auth.js (+12 -1)
📝 server/Server.js (+44 -30)

📄 Description

Brief summary

When ENV variable REACT_CLIENT_PATH is set the server will start a next.js app at the location instead of serving the nuxt app.

This is for testing a separate React frontend.

In-depth Description

As of now the goal is to replace Nuxt with React (probably Next but not certain) and to keep the frontend in a separate repo from the server.

In the following days I'll set up a repo for the client. I have one on my local that is working well but needs to be cleaned up.

Some of the main reasons for choosing Next:

  • Works with CJS (including SSR)
  • pkg can create binaries for Windows/Debian
  • HMR in development works out-of-the-box without running another process

🔄 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/4430 **Author:** [@advplyr](https://github.com/advplyr) **Created:** 6/24/2025 **Status:** ✅ Merged **Merged:** 6/24/2025 **Merged by:** [@advplyr](https://github.com/advplyr) **Base:** `master` ← **Head:** `experimental_next_client` --- ### 📝 Commits (1) - [`a992400`](https://github.com/advplyr/audiobookshelf/commit/a992400d6abd9ca96e9b637e987ec46e4fbc5a08) Add ENV REACT_CLIENT_PATH to target a Nextjs frontend instead of Nuxt ### 📊 Changes **3 files changed** (+57 additions, -31 deletions) <details> <summary>View changed files</summary> 📝 `index.js` (+1 -0) 📝 `server/Auth.js` (+12 -1) 📝 `server/Server.js` (+44 -30) </details> ### 📄 Description <!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. If you do not follow this template, the PR may be closed without review. Please ensure all checks pass. If you are a new contributor, the workflows will need to be manually approved before they run. --> ## Brief summary When ENV variable `REACT_CLIENT_PATH` is set the server will start a next.js app at the location instead of serving the nuxt app. This is for testing a separate React frontend. ## In-depth Description As of now the goal is to replace Nuxt with React (probably Next but not certain) and to keep the frontend in a separate repo from the server. In the following days I'll set up a repo for the client. I have one on my local that is working well but needs to be cleaned up. Some of the main reasons for choosing Next: - Works with CJS (including SSR) - `pkg` can create binaries for Windows/Debian - HMR in development works out-of-the-box without running another process --- <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:19:00 +02:00
adam closed this issue 2026-04-25 00:19:00 +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#4248
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?