You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Node version: 20.18.0
NPM version: 10.8.2
OS: Windows 11
Looks like I'm unable to run migrations anymore, creating a new migration file works without any problem but when I try to run the migration it gives me this error:
An error ocurred when run the migration file: 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:'
Command I used to run the migration: storyblok run-migration --space 296527 --component meta-info --field meta_title --dryrun
The text was updated successfully, but these errors were encountered:
I am also seeing the same error, but when running the storyblok generate-typescript-typedefs command with the --customFieldTypesParserPath parameter.
It looks to be because of this line, const customTypeParser = await import(resolve(path)).
If I pass ./path/to/file.js as the argument to the above parameter, resolve on Windows is creating a Windows file path like C:\path\to\file.js, which can't be used by import and throws an ERR_UNSUPPORTED_ESM_URL_SCHEME error.
Node version: 20.18.0
NPM version: 10.8.2
OS: Windows 11
Looks like I'm unable to run migrations anymore, creating a new migration file works without any problem but when I try to run the migration it gives me this error:
An error ocurred when run the migration file: 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:'
Command I used to run the migration:
storyblok run-migration --space 296527 --component meta-info --field meta_title --dryrun
The text was updated successfully, but these errors were encountered: