github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 03:32:54 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Bug]: After @actual-app/api 6.8.0 npm install fails #1129

New Issue
Closed
opened 2026-02-28 19:33:09 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-02-28 19:33:09 -06:00
Owner
Copy Link

Originally created by @jhonderson on GitHub (Jun 4, 2024).

Originally assigned to: @twk3 on GitHub.

Verified issue does not already exist?

  • I have searched and found no existing issue
  • I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file)

What happened?

After latest release, installing actual api using npm fails:

$ npm install --save @actual-app/api
npm error code EUNSUPPORTEDPROTOCOL
npm error Unsupported URL Type "workspace:": workspace:^
npm error A complete log of this run can be found in: ....log

It's probably caused by this commit f604fdaf36.

My env:

$ npm --version
7.24.2
$ node -v
v20.10.0

yarn install works, so I am not sure if the documentation should be updated to switch to yarn.

I have a project installing the actual nodejs library using npm, please let me know if npm will no longer be supported so that I can switch to yarn.

Thanks!

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Other

Operating System

Mac OSX

Originally created by @jhonderson on GitHub (Jun 4, 2024). Originally assigned to: @twk3 on GitHub. ### Verified issue does not already exist? - [X] I have searched and found no existing issue - [X] I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file) ### What happened? After latest release, installing actual api using npm fails: ``` $ npm install --save @actual-app/api npm error code EUNSUPPORTEDPROTOCOL npm error Unsupported URL Type "workspace:": workspace:^ npm error A complete log of this run can be found in: ....log ``` It's probably caused by this commit https://github.com/actualbudget/actual/commit/f604fdaf3616d056b899ae824f97bdda476d4cee. My env: ``` $ npm --version 7.24.2 $ node -v v20.10.0 ``` `yarn install` works, so I am not sure if the documentation should be updated to switch to yarn. I have a project installing the actual nodejs library using npm, please let me know if npm will no longer be supported so that I can switch to yarn. Thanks! ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Other ### Operating System Mac OSX
GiteaMirror added the bug label 2026-02-28 19:33:09 -06:00
GiteaMirror commented 2026-02-28 19:33:11 -06:00
Author
Owner
Copy Link

@MattFaz commented on GitHub (Jun 5, 2024):

Exactly the same happening to me, with yarn I get the following:

yarn install v1.22.22
info No lockfile found.
[1/4] 🔍  Resolving packages...
Couldn't find any versions for "@actual-app/crdt" that matches "workspace:^"
? Please choose a version of "@actual-app/crdt" from this list: (Use arrow keys)
❯ 2.1.0 
  2.0.2 
  2.0.1 
  2.0.0 
  1.0.0
@MattFaz commented on GitHub (Jun 5, 2024): Exactly the same happening to me, with yarn I get the following: ``` yarn install v1.22.22 info No lockfile found. [1/4] 🔍 Resolving packages... Couldn't find any versions for "@actual-app/crdt" that matches "workspace:^" ? Please choose a version of "@actual-app/crdt" from this list: (Use arrow keys) ❯ 2.1.0 2.0.2 2.0.1 2.0.0 1.0.0 ```
GiteaMirror commented 2026-02-28 19:33:11 -06:00
Author
Owner
Copy Link

@jhonderson commented on GitHub (Jun 5, 2024):

@MattFaz yep same here for yarn. Since I haven’t used yarn with Actual before, I thought it was normal.

@jhonderson commented on GitHub (Jun 5, 2024): @MattFaz yep same here for yarn. Since I haven’t used yarn with Actual before, I thought it was normal.
GiteaMirror commented 2026-02-28 19:33:11 -06:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Jun 6, 2024):

@twk3 any ideas?

@MatissJanis commented on GitHub (Jun 6, 2024): @twk3 any ideas?
GiteaMirror commented 2026-02-28 19:33:11 -06:00
Author
Owner
Copy Link

@twk3 commented on GitHub (Jun 6, 2024):

whoops, that use of workspace should have only been there like that if it was a dev dependency. I'll get that fixed.

@twk3 commented on GitHub (Jun 6, 2024): whoops, that use of workspace should have only been there like that if it was a dev dependency. I'll get that fixed.
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#1129
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?