github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 20:15:33 -05:00
Code Issues 1.6k Packages Projects Releases 55 Wiki Activity

[GH-ISSUE #4377] [Bug]: yarn install:server does not work #16098

New Issue
Closed
opened 2026-04-14 19:15:41 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-14 19:15:41 -05:00
Owner
Copy Link

Originally created by @pogman-code on GitHub (Feb 14, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/4377

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

The new script yarn install:server does not work out of the box but yarn workspaces focus actual-sync --production does.

As per the documentation (https://actualbudget.org/docs/install/local#installing-actual) it seems that it should work.
I tried with several version of node/npm with the same result, above example uses v18.16.0 as specified in .nvmrc

I looked a bit online but most answer suggest to run yarn install first, that kind of lose the purpose of yarn install:server that is supposed to perform a "light" install, right?

How can we reproduce the issue?

user@localhost ~ $ git clone https://github.com/actualbudget/actual.git               
Cloning into 'actual'...
remote: Enumerating objects: 55157, done.
remote: Counting objects: 100% (402/402), done.
remote: Compressing objects: 100% (276/276), done.
remote: Total 55157 (delta 243), reused 130 (delta 126), pack-reused 54755 (from 3)
Receiving objects: 100% (55157/55157), 210.86 MiB | 40.61 MiB/s, done.
Resolving deltas: 100% (39757/39757), done.



user@localhost ~ $ cd actual 
Found '/home/user/actual/.nvmrc' with version <v18.16.0>
Downloading and installing node v18.16.0...
Downloading https://nodejs.org/dist/v18.16.0/node-v18.16.0-linux-x64.tar.xz...
######################################################################################################################################################################################################################################################################################################################## 100.0%
Computing checksum with sha256sum
Checksums matched!
Now using node v18.16.0 (npm v9.5.1)



user@localhost actual (master v23.1.12+) $ yarn install:server         
Usage Error: Couldn't find the node_modules state file - running an install might help (findPackageLocation)

$ yarn run [--inspect] [--inspect-brk] [-T,--top-level] [-B,--binaries-only] [--require #0] <scriptName> ...



user@localhost actual (master v23.1.12+) $ yarn workspaces focus actual-sync --production
➤ YN0000: · Yarn 4.3.1
➤ YN0000: ┌ Resolution step
➤ YN0085: │ - 7zip-bin@npm:5.2.0, @aashutoshrathi/word-wrap@npm:1.2.6, @ampproject/remapping@npm:2.2.1, @antfu/utils@npm:0.7.10, @apideck/better-ajv-errors@npm:0.3.6, @babel/code-frame@npm:7.24.7, @babel/code-frame@npm:7.26.2, @babel/compat-data@npm:7.23.5, @babel/compat-data@npm:7.26.5, and 1911 more.
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0013: │ 277 packages were added to the project (+ 18.54 MiB).
➤ YN0000: └ Completed in 2s 170ms
➤ YN0000: ┌ Link step
➤ YN0007: │ bcrypt@npm:5.1.1 must be built because it never has been before or the last one failed
➤ YN0007: │ better-sqlite3@npm:11.7.0 must be built because it never has been before or the last one failed
➤ YN0000: └ Completed in 1s 692ms
➤ YN0000: · Done in 3s 951ms

Where are you hosting Actual?

Locally via Yarn

What browsers are you seeing the problem on?

Other

Operating System

Linux

Originally created by @pogman-code on GitHub (Feb 14, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/4377 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? The new script `yarn install:server` does not work out of the box but `yarn workspaces focus actual-sync --production` does. As per the documentation (https://actualbudget.org/docs/install/local#installing-actual) it seems that it should work. I tried with several version of node/npm with the same result, above example uses v18.16.0 as specified in `.nvmrc` I looked a bit online but most answer suggest to run `yarn install` first, that kind of lose the purpose of `yarn install:server` that is supposed to perform a "light" install, right? ### How can we reproduce the issue? ```sh user@localhost ~ $ git clone https://github.com/actualbudget/actual.git Cloning into 'actual'... remote: Enumerating objects: 55157, done. remote: Counting objects: 100% (402/402), done. remote: Compressing objects: 100% (276/276), done. remote: Total 55157 (delta 243), reused 130 (delta 126), pack-reused 54755 (from 3) Receiving objects: 100% (55157/55157), 210.86 MiB | 40.61 MiB/s, done. Resolving deltas: 100% (39757/39757), done. user@localhost ~ $ cd actual Found '/home/user/actual/.nvmrc' with version <v18.16.0> Downloading and installing node v18.16.0... Downloading https://nodejs.org/dist/v18.16.0/node-v18.16.0-linux-x64.tar.xz... ######################################################################################################################################################################################################################################################################################################################## 100.0% Computing checksum with sha256sum Checksums matched! Now using node v18.16.0 (npm v9.5.1) user@localhost actual (master v23.1.12+) $ yarn install:server Usage Error: Couldn't find the node_modules state file - running an install might help (findPackageLocation) $ yarn run [--inspect] [--inspect-brk] [-T,--top-level] [-B,--binaries-only] [--require #0] <scriptName> ... user@localhost actual (master v23.1.12+) $ yarn workspaces focus actual-sync --production ➤ YN0000: · Yarn 4.3.1 ➤ YN0000: ┌ Resolution step ➤ YN0085: │ - 7zip-bin@npm:5.2.0, @aashutoshrathi/word-wrap@npm:1.2.6, @ampproject/remapping@npm:2.2.1, @antfu/utils@npm:0.7.10, @apideck/better-ajv-errors@npm:0.3.6, @babel/code-frame@npm:7.24.7, @babel/code-frame@npm:7.26.2, @babel/compat-data@npm:7.23.5, @babel/compat-data@npm:7.26.5, and 1911 more. ➤ YN0000: └ Completed ➤ YN0000: ┌ Fetch step ➤ YN0013: │ 277 packages were added to the project (+ 18.54 MiB). ➤ YN0000: └ Completed in 2s 170ms ➤ YN0000: ┌ Link step ➤ YN0007: │ bcrypt@npm:5.1.1 must be built because it never has been before or the last one failed ➤ YN0007: │ better-sqlite3@npm:11.7.0 must be built because it never has been before or the last one failed ➤ YN0000: └ Completed in 1s 692ms ➤ YN0000: · Done in 3s 951ms ``` ### Where are you hosting Actual? Locally via Yarn ### What browsers are you seeing the problem on? Other ### Operating System Linux
GiteaMirror added the bug label 2026-04-14 19:15:41 -05:00
GiteaMirror commented 2026-04-14 19:15:43 -05:00
Author
Owner
Copy Link

@MikesGlitch commented on GitHub (Feb 15, 2025):

Thanks for raising. Looks like an annoying yarn issue - it doesn't let you run scripts unless you've done an install 🤦‍♂ . Funnily enough, npm seems to work:

npm run install:server

I'll have a look. We may have to remove the script.

<!-- gh-comment-id:2661027374 --> @MikesGlitch commented on GitHub (Feb 15, 2025): Thanks for raising. Looks like an annoying yarn issue - it doesn't let you run scripts unless you've done an install 🤦‍♂ . Funnily enough, npm seems to work: ``` npm run install:server ``` I'll have a look. We may have to remove the script.
GiteaMirror commented 2026-04-14 19:15:44 -05:00
Author
Owner
Copy Link

@pogman-code commented on GitHub (Feb 15, 2025):

I have seen some discussions about this being an issue with recent versions of yarn.

I guess as long as we can run yarn workspaces focus actual-sync --production, that OK 🤷

<!-- gh-comment-id:2661116961 --> @pogman-code commented on GitHub (Feb 15, 2025): I have seen some discussions about this being an issue with recent versions of yarn. I guess as long as we can run `yarn workspaces focus actual-sync --production`, that OK 🤷
GiteaMirror commented 2026-04-14 19:15:45 -05:00
Author
Owner
Copy Link

@MikesGlitch commented on GitHub (Feb 17, 2025):

Have updated the docs: https://github.com/actualbudget/docs/pull/645

The change is to run the command without the script for now. Closing this.

<!-- gh-comment-id:2662500894 --> @MikesGlitch commented on GitHub (Feb 17, 2025): Have updated the docs: https://github.com/actualbudget/docs/pull/645 The change is to run the command without the script for now. Closing this.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#16098
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?