github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-16 07:04:23 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #1905] [Bug]: ERR_UNSUPPORTED_ESM_URL_SCHEME #49852

New Issue
Closed
opened 2026-04-30 11:43:53 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-30 11:43:53 -05:00
Owner
Copy Link

Originally created by @th3c0d3br34ker on GitHub (Nov 14, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1905

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Unable to run yarn start using actualbudget/actual-server on windows.

Node version: v18.16.1
actualbudget/actual-server version: v23.11.0

What error did you receive?

Checking if there are any migrations to run for direction "up"...
Rejection: Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file and data are supported by the default 
ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'e:'
    at new NodeError (node:internal/errors:399:5)
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/resolve:1059:11)
    at defaultResolve (node:internal/modules/esm/resolve:1135:3)
    at nextResolve (node:internal/modules/esm/loader:163:28)
    at ESMLoader.resolve (node:internal/modules/esm/loader:838:30)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
    at ESMLoader.import (node:internal/modules/esm/loader:525:22)
    at importModuleDynamically (node:internal/modules/cjs/loader:1188:29)
    at importModuleDynamicallyWrapper (node:internal/vm/module:429:21)
    at importModuleDynamically (node:internal/vm:106:46) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}

Where are you hosting Actual?

Locally via Yarn

What browsers are you seeing the problem on?

No response

Operating System

Windows 11

Originally created by @th3c0d3br34ker on GitHub (Nov 14, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/1905 ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? Unable to run `yarn start` using `actualbudget/actual-server` on windows. Node version: `v18.16.1` `actualbudget/actual-server` version: `v23.11.0` ### What error did you receive? ```bash Checking if there are any migrations to run for direction "up"... Rejection: Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file and data are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'e:' at new NodeError (node:internal/errors:399:5) at throwIfUnsupportedURLScheme (node:internal/modules/esm/resolve:1059:11) at defaultResolve (node:internal/modules/esm/resolve:1135:3) at nextResolve (node:internal/modules/esm/loader:163:28) at ESMLoader.resolve (node:internal/modules/esm/loader:838:30) at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18) at ESMLoader.import (node:internal/modules/esm/loader:525:22) at importModuleDynamically (node:internal/modules/cjs/loader:1188:29) at importModuleDynamicallyWrapper (node:internal/vm/module:429:21) at importModuleDynamically (node:internal/vm:106:46) { code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME' } ``` ### Where are you hosting Actual? Locally via Yarn ### What browsers are you seeing the problem on? _No response_ ### Operating System Windows 11
GiteaMirror added the bug label 2026-04-30 11:43:53 -05:00
GiteaMirror commented 2026-04-30 11:44:08 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Nov 16, 2023):

https://github.com/tj/node-migrate/issues/201

<!-- gh-comment-id:1814006898 --> @MatissJanis commented on GitHub (Nov 16, 2023): https://github.com/tj/node-migrate/issues/201
GiteaMirror commented 2026-04-30 11:44:16 -05:00
Author
Owner
Copy Link

@MrScriptX commented on GitHub (Nov 17, 2023):

Maybe a temporary fork to fix the issue should be done, or maybe a downgrade ? Currently, actual is broken on Windows and the issue link is open since August with no PR opened yet.

<!-- gh-comment-id:1816173189 --> @MrScriptX commented on GitHub (Nov 17, 2023): Maybe a temporary fork to fix the issue should be done, or maybe a downgrade ? Currently, actual is broken on Windows and the issue link is open since August with no PR opened yet.
GiteaMirror commented 2026-04-30 11:44:18 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Nov 18, 2023):

I don't have Windows, so sadly I can't reproduce and thus fix it. If anyone is able to repro: a patch PR would be more than welcome.

In the meantime I would recommend using the docker version of Actual. That will work in all environments

https://actualbudget.org/docs/install/docker#launch-container-using-docker-command

<!-- gh-comment-id:1817508897 --> @MatissJanis commented on GitHub (Nov 18, 2023): I don't have Windows, so sadly I can't reproduce and thus fix it. If anyone is able to repro: a patch PR would be more than welcome. In the meantime I would recommend using the docker version of Actual. That will work in all environments https://actualbudget.org/docs/install/docker#launch-container-using-docker-command
GiteaMirror commented 2026-04-30 11:44:19 -05:00
Author
Owner
Copy Link

@MikesGlitch commented on GitHub (Nov 19, 2023):

I fixed the migrate package for windows here (the PR is in draft): https://github.com/tj/node-migrate/pull/202

I think it should work but would someone on Linux be able to check it still works there?

If you clone it down you can just update your Actual Server package.json "migrate" dependency with:

"migrate": "file:../node-migrate",

where the path is the path to the repo.

<!-- gh-comment-id:1817851789 --> @MikesGlitch commented on GitHub (Nov 19, 2023): I fixed the migrate package for windows here (the PR is in draft): https://github.com/tj/node-migrate/pull/202 I think it should work but would someone on Linux be able to check it still works there? If you clone it down you can just update your Actual Server package.json "migrate" dependency with: "migrate": "file:../node-migrate", where the path is the path to the repo.
GiteaMirror commented 2026-04-30 11:44:20 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Nov 22, 2023):

Should be solved now. Please let us know if the issue still persists.

<!-- gh-comment-id:1823574314 --> @MatissJanis commented on GitHub (Nov 22, 2023): Should be solved now. Please let us know if the issue still persists.
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
tech-support
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#49852
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?