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

[Bug]: ERR_UNSUPPORTED_ESM_URL_SCHEME #2893

New Issue
Closed
opened 2026-02-28 20:31:49 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-02-28 20:31:49 -06:00
Owner
Copy Link

Originally created by @S3rrrjjj on GitHub (Feb 5, 2026).

Originally assigned to: @MikesGlitch on GitHub.

What happened?

v26.2.0
Windows 11
Server does not start

How can we reproduce the issue?

Server does not start after yarn start:server. Updating node.js didn't fix the problem.

Error message:

Checking if there are any migrations to run for direction "up"...
Error during migration process: Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be va
lid file:// URLs. Received protocol 'c:'
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:208:11)
    at defaultLoad (node:internal/modules/esm/load:103:3)
    at ModuleLoader.load (node:internal/modules/esm/loader:739:12)
    at ModuleLoader.loadAndTranslate (node:internal/modules/esm/loader:519:43)
    at #createModuleJob (node:internal/modules/esm/loader:543:36)
    at #getJobFromResolveResult (node:internal/modules/esm/loader:312:34)
    at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:280:41)
    at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:582:25) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}
Error starting app: Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file://
URLs. Received protocol 'c:'
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:208:11)
    at defaultLoad (node:internal/modules/esm/load:103:3)
    at ModuleLoader.load (node:internal/modules/esm/loader:739:12)
    at ModuleLoader.loadAndTranslate (node:internal/modules/esm/loader:519:43)
    at #createModuleJob (node:internal/modules/esm/loader:543:36)
    at #getJobFromResolveResult (node:internal/modules/esm/loader:312:34)
    at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:280:41)
    at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:582:25) {
  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 @S3rrrjjj on GitHub (Feb 5, 2026). Originally assigned to: @MikesGlitch on GitHub. ### What happened? v26.2.0 Windows 11 Server does not start ### How can we reproduce the issue? Server does not start after `yarn start:server`. Updating node.js didn't fix the problem. Error message: ``` Checking if there are any migrations to run for direction "up"... Error during migration process: Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be va lid file:// URLs. Received protocol 'c:' at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:208:11) at defaultLoad (node:internal/modules/esm/load:103:3) at ModuleLoader.load (node:internal/modules/esm/loader:739:12) at ModuleLoader.loadAndTranslate (node:internal/modules/esm/loader:519:43) at #createModuleJob (node:internal/modules/esm/loader:543:36) at #getJobFromResolveResult (node:internal/modules/esm/loader:312:34) at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:280:41) at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:582:25) { code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME' } Error starting app: Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:' at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:208:11) at defaultLoad (node:internal/modules/esm/load:103:3) at ModuleLoader.load (node:internal/modules/esm/loader:739:12) at ModuleLoader.loadAndTranslate (node:internal/modules/esm/loader:519:43) at #createModuleJob (node:internal/modules/esm/loader:543:36) at #getJobFromResolveResult (node:internal/modules/esm/loader:312:34) at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:280:41) at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:582:25) { 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-02-28 20:31:49 -06:00
GiteaMirror commented 2026-02-28 20:31:50 -06:00
Author
Owner
Copy Link

@S3rrrjjj commented on GitHub (Feb 5, 2026):

Switched to CLI tool and it's working now

@S3rrrjjj commented on GitHub (Feb 5, 2026): Switched to CLI tool and it's working now
GiteaMirror commented 2026-02-28 20:31:50 -06:00
Author
Owner
Copy Link

@lyric911 commented on GitHub (Feb 23, 2026):

@S3rrrjjj I am having this same issue. Can you please share more information about how you fixed? I'm not sure what 'Switched to CLI tool and it's working now' means.

@lyric911 commented on GitHub (Feb 23, 2026): @S3rrrjjj I am having this same issue. Can you please share more information about how you fixed? I'm not sure what 'Switched to CLI tool and it's working now' means.
GiteaMirror commented 2026-02-28 20:31:50 -06:00
Author
Owner
Copy Link

@S3rrrjjj commented on GitHub (Feb 23, 2026):

Followed this to install the server in a new folder: https://actualbudget.org/docs/install/cli-tool

@S3rrrjjj commented on GitHub (Feb 23, 2026): Followed this to install the server in a new folder: https://actualbudget.org/docs/install/cli-tool
GiteaMirror commented 2026-02-28 20:31:51 -06:00
Author
Owner
Copy Link

@MikesGlitch commented on GitHub (Feb 25, 2026):

This is a bug in latest master, thanks for reporting

@MikesGlitch commented on GitHub (Feb 25, 2026): This is a bug in latest master, thanks for reporting
GiteaMirror commented 2026-02-28 20:31:51 -06:00
Author
Owner
Copy Link

@MikesGlitch commented on GitHub (Feb 25, 2026):

Tracked it down to https://github.com/actualbudget/actual/pull/6346

@MikesGlitch commented on GitHub (Feb 25, 2026): Tracked it down to https://github.com/actualbudget/actual/pull/6346
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#2893
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?