github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 07:01:45 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[GH-ISSUE #4310] [Bug]: ERR_UNSUPPORTED_ESM_URL_SCHEME #8770

New Issue
Closed
opened 2026-04-10 19:03:18 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-10 19:03:18 -05:00
Owner
Copy Link

Originally created by @mbrijun on GitHub (Feb 6, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/4310

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Following the latest "git pull" of the actual-server's main branch, I am now getting "ERR_UNSUPPORTED_ESM_URL_SCHEME".

PS C:\tools\actual-server> git pull
remote: Enumerating objects: 11, done.
remote: Counting objects: 100% (10/10), done.
remote: Compressing objects: 100% (8/8), done.
remote: Total 11 (delta 3), reused 4 (delta 2), pack-reused 1 (from 1)
Unpacking objects: 100% (11/11), 89.63 KiB | 2.64 MiB/s, done.
From https://github.com/actualbudget/actual-server
   0312f51..abeeb05  master     -> origin/master
 * [new tag]         v25.2.0    -> v25.2.0
Updating 0312f51..abeeb05
Fast-forward
 package.json                              |   4 +-
 src/app-gocardless/bank-factory.js        | 102 +++++++-----------------------
 upcoming-release-notes/499.md             |   6 --
 upcoming-release-notes/531.md             |   6 --
 upcoming-release-notes/533.md             |   6 --
 upcoming-release-notes/534.md             |   6 --
 upcoming-release-notes/535.md             |   6 --
 upcoming-release-notes/537.md             |   6 --
 upcoming-release-notes/538.md             |   6 --
 upcoming-release-notes/539.md             |   6 --
 upcoming-release-notes/542.md             |   6 --
 upcoming-release-notes/546.md             |   6 --
 upcoming-release-notes/547.md             |   6 --
 upcoming-release-notes/550.md             |   6 --
 upcoming-release-notes/551.md             |   6 --
 upcoming-release-notes/553.md             |   6 --
 upcoming-release-notes/554.md             |   6 --
 upcoming-release-notes/{541.md => 557.md} |   2 +-
 yarn.lock                                 |  10 +--
 19 files changed, 32 insertions(+), 176 deletions(-)
 delete mode 100644 upcoming-release-notes/499.md
 delete mode 100644 upcoming-release-notes/531.md
 delete mode 100644 upcoming-release-notes/533.md
 delete mode 100644 upcoming-release-notes/534.md
 delete mode 100644 upcoming-release-notes/535.md
 delete mode 100644 upcoming-release-notes/537.md
 delete mode 100644 upcoming-release-notes/538.md
 delete mode 100644 upcoming-release-notes/539.md
 delete mode 100644 upcoming-release-notes/542.md
 delete mode 100644 upcoming-release-notes/546.md
 delete mode 100644 upcoming-release-notes/547.md
 delete mode 100644 upcoming-release-notes/550.md
 delete mode 100644 upcoming-release-notes/551.md
 delete mode 100644 upcoming-release-notes/553.md
 delete mode 100644 upcoming-release-notes/554.md
 rename upcoming-release-notes/{541.md => 557.md} (58%)
PS C:\tools\actual-server> git pull
Already up to date.
PS C:\tools\actual-server> yarn install
➤ YN0088: A new stable version of Yarn is available: 4.6.0!
➤ YN0088: Upgrade now by running yarn set version 4.6.0

➤ YN0000: · Yarn 4.3.1
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed
➤ YN0000: ┌ Post-resolution validation
➤ YN0002: │ actual-sync@workspace:. doesn't provide @babel/core (p89c81), requested by @babel/preset-typescript.
➤ YN0086: │ Some peer dependencies are incorrectly met by your project; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code.
➤ YN0086: │ Some peer dependencies are incorrectly met by dependencies; run yarn explain peer-requirements for details.
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0013: │ A package was added to the project (+ 23.93 MiB).
➤ YN0000: └ Completed in 3s 859ms
➤ YN0000: ┌ Link step
➤ YN0000: └ Completed in 0s 511ms
➤ YN0000: · Done with warnings in 4s 619ms
PS C:\tools\actual-server> yarn start
Checking if there are any migrations to run for direction "up"...
Migrations: DONE
node:internal/modules/esm/load:249
    throw new ERR_UNSUPPORTED_ESM_URL_SCHEME(parsed, schemes);
          ^

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:249:11)
    at defaultLoad (node:internal/modules/esm/load:130:3)
    at ModuleLoader.load (node:internal/modules/esm/loader:555:13)
    at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:434:56)
    at new ModuleJob (node:internal/modules/esm/module_job:71:27)
    at #createModuleJob (node:internal/modules/esm/loader:447:17)
    at ModuleLoader.getJobFromResolveResult (node:internal/modules/esm/loader:259:34)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:240:17)
    at async ModuleLoader.import (node:internal/modules/esm/loader:472:23) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}

Node.js v20.18.0

How can we reproduce the issue?

  1. git pull
  2. yarn install
  3. yarn start

Where are you hosting Actual?

Locally via Yarn

What browsers are you seeing the problem on?

Firefox

Operating System

Windows 11

Originally created by @mbrijun on GitHub (Feb 6, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/4310 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? Following the latest "git pull" of the actual-server's main branch, I am now getting "ERR_UNSUPPORTED_ESM_URL_SCHEME". ``` PS C:\tools\actual-server> git pull remote: Enumerating objects: 11, done. remote: Counting objects: 100% (10/10), done. remote: Compressing objects: 100% (8/8), done. remote: Total 11 (delta 3), reused 4 (delta 2), pack-reused 1 (from 1) Unpacking objects: 100% (11/11), 89.63 KiB | 2.64 MiB/s, done. From https://github.com/actualbudget/actual-server 0312f51..abeeb05 master -> origin/master * [new tag] v25.2.0 -> v25.2.0 Updating 0312f51..abeeb05 Fast-forward package.json | 4 +- src/app-gocardless/bank-factory.js | 102 +++++++----------------------- upcoming-release-notes/499.md | 6 -- upcoming-release-notes/531.md | 6 -- upcoming-release-notes/533.md | 6 -- upcoming-release-notes/534.md | 6 -- upcoming-release-notes/535.md | 6 -- upcoming-release-notes/537.md | 6 -- upcoming-release-notes/538.md | 6 -- upcoming-release-notes/539.md | 6 -- upcoming-release-notes/542.md | 6 -- upcoming-release-notes/546.md | 6 -- upcoming-release-notes/547.md | 6 -- upcoming-release-notes/550.md | 6 -- upcoming-release-notes/551.md | 6 -- upcoming-release-notes/553.md | 6 -- upcoming-release-notes/554.md | 6 -- upcoming-release-notes/{541.md => 557.md} | 2 +- yarn.lock | 10 +-- 19 files changed, 32 insertions(+), 176 deletions(-) delete mode 100644 upcoming-release-notes/499.md delete mode 100644 upcoming-release-notes/531.md delete mode 100644 upcoming-release-notes/533.md delete mode 100644 upcoming-release-notes/534.md delete mode 100644 upcoming-release-notes/535.md delete mode 100644 upcoming-release-notes/537.md delete mode 100644 upcoming-release-notes/538.md delete mode 100644 upcoming-release-notes/539.md delete mode 100644 upcoming-release-notes/542.md delete mode 100644 upcoming-release-notes/546.md delete mode 100644 upcoming-release-notes/547.md delete mode 100644 upcoming-release-notes/550.md delete mode 100644 upcoming-release-notes/551.md delete mode 100644 upcoming-release-notes/553.md delete mode 100644 upcoming-release-notes/554.md rename upcoming-release-notes/{541.md => 557.md} (58%) PS C:\tools\actual-server> git pull Already up to date. PS C:\tools\actual-server> yarn install ➤ YN0088: A new stable version of Yarn is available: 4.6.0! ➤ YN0088: Upgrade now by running yarn set version 4.6.0 ➤ YN0000: · Yarn 4.3.1 ➤ YN0000: ┌ Resolution step ➤ YN0000: └ Completed ➤ YN0000: ┌ Post-resolution validation ➤ YN0002: │ actual-sync@workspace:. doesn't provide @babel/core (p89c81), requested by @babel/preset-typescript. ➤ YN0086: │ Some peer dependencies are incorrectly met by your project; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code. ➤ YN0086: │ Some peer dependencies are incorrectly met by dependencies; run yarn explain peer-requirements for details. ➤ YN0000: └ Completed ➤ YN0000: ┌ Fetch step ➤ YN0013: │ A package was added to the project (+ 23.93 MiB). ➤ YN0000: └ Completed in 3s 859ms ➤ YN0000: ┌ Link step ➤ YN0000: └ Completed in 0s 511ms ➤ YN0000: · Done with warnings in 4s 619ms PS C:\tools\actual-server> yarn start Checking if there are any migrations to run for direction "up"... Migrations: DONE node:internal/modules/esm/load:249 throw new ERR_UNSUPPORTED_ESM_URL_SCHEME(parsed, schemes); ^ 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:249:11) at defaultLoad (node:internal/modules/esm/load:130:3) at ModuleLoader.load (node:internal/modules/esm/loader:555:13) at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:434:56) at new ModuleJob (node:internal/modules/esm/module_job:71:27) at #createModuleJob (node:internal/modules/esm/loader:447:17) at ModuleLoader.getJobFromResolveResult (node:internal/modules/esm/loader:259:34) at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:240:17) at async ModuleLoader.import (node:internal/modules/esm/loader:472:23) { code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME' } Node.js v20.18.0 ``` ### How can we reproduce the issue? 1. git pull 2. yarn install 3. yarn start ### Where are you hosting Actual? Locally via Yarn ### What browsers are you seeing the problem on? Firefox ### Operating System Windows 11
GiteaMirror added the bug label 2026-04-10 19:03:18 -05:00
GiteaMirror commented 2026-04-10 19:03:19 -05:00
Author
Owner
Copy Link

@deftly1970 commented on GitHub (Feb 6, 2025):

I am getting this same error on Windows 11. I have installs on two different machines, both running Windows 11, and they both threw the same error.

<!-- gh-comment-id:2639268756 --> @deftly1970 commented on GitHub (Feb 6, 2025): I am getting this same error on Windows 11. I have installs on two different machines, both running Windows 11, and they both threw the same error.
GiteaMirror commented 2026-04-10 19:03:19 -05:00
Author
Owner
Copy Link

@rzh90 commented on GitHub (Feb 6, 2025):

Same issue for me on Windows 11. Upgraded to Node.js 22.13.1 and still didn't work.

<!-- gh-comment-id:2639528287 --> @rzh90 commented on GitHub (Feb 6, 2025): Same issue for me on Windows 11. Upgraded to Node.js 22.13.1 and still didn't work.
GiteaMirror commented 2026-04-10 19:03:20 -05:00
Author
Owner
Copy Link

@mrcbt commented on GitHub (Feb 6, 2025):

Same issue here. Also upgraded to node.js 22.13.1 and it didnt' work.

Reinstalled actual didnt work.

EDIT:
Reverted to the old working version by using: git checkout 95180cc

<!-- gh-comment-id:2639605199 --> @mrcbt commented on GitHub (Feb 6, 2025): Same issue here. Also upgraded to node.js 22.13.1 and it didnt' work. Reinstalled actual didnt work. EDIT: Reverted to the old working version by using: git checkout 95180cc
GiteaMirror commented 2026-04-10 19:03:20 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Feb 6, 2025):

This should be fixed on edge (and maybe on v25.2.1, maybe try that). Can anyone here confirm?

<!-- gh-comment-id:2641181871 --> @youngcw commented on GitHub (Feb 6, 2025): This should be fixed on edge (and maybe on v25.2.1, maybe try that). Can anyone here confirm?
GiteaMirror commented 2026-04-10 19:03:20 -05:00
Author
Owner
Copy Link

@deftly1970 commented on GitHub (Feb 6, 2025):

This should be fixed on edge (and maybe on v25.2.1, maybe try that). Can anyone here confirm?

I can confirm that v25.2.1 fixed my install. Thanks!

<!-- gh-comment-id:2641314879 --> @deftly1970 commented on GitHub (Feb 6, 2025): > This should be fixed on edge (and maybe on v25.2.1, maybe try that). Can anyone here confirm? I can confirm that v25.2.1 fixed my install. Thanks!
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#8770
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?