-
-
Notifications
You must be signed in to change notification settings - Fork 690
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.1.2 broken #990
Comments
Can you please elaborate the steps to reproduce? |
[4/4] Building fresh packages...
[1/4] ⠁ maplibre-gl
[-/4] ⠁ waiting...
[3/4] ⠁ core-js
error D:\projects\gis-admin\node_modules\maplibre-gl: Command failed.
Exit code: 1
Command: npm run codegen && npm run generate-query-test-fixtures
Arguments:
Directory: D:\projects\gis-admin\node_modules\maplibre-gl
Output:
> [email protected] codegen
> npm run generate-style-code && npm run generate-struct-arrays && npm run generate-style-spec && npm run generate-shaders
> [email protected] generate-style-code
> node --loader ts-node/esm --experimental-specifier-resolution=node build/generate-style-code.ts
(node:2952) ExperimentalWarning: --experimental-loader is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
(node:2952) ExperimentalWarning: The Node.js specifier resolution in ESM is experimental.
(node:2952) ExperimentalWarning: The Node.js specifier resolution in ESM is experimental.
TypeError [ERR_INVALID_MODULE_SPECIFIER]: Invalid module "file:///D:/projects/gis-admin/node_modules/maplibre-gl/build/generate-style-code.ts"
at new NodeError (node:internal/errors:371:5)
at ESMLoader.load (node:internal/modules/esm/loader:324:13)
at async ESMLoader.moduleProvider (node:internal/modules/esm/loader:230:47)
at async link (node:internal/modules/esm/module_job:67:21) { |
Yes, looks like the post install. Thanks for reporting! If you are familiar with post install that will happen only when using npm install for this repo it will help a lot! |
This is probably the solution: |
I am running into a similar issue this morning, this works with version
It might be a different issue, since it's talking about I created a very simple package.json: (I also tried it as a dependency on both machines)
This is the error I get when I run npm install
|
According to SO |
Workaround: |
btw please consider introducing beta builds. |
Good idea, thanks for the feedback. |
Attempted a solution with #991, but this created a new problem:
|
The problem is: we do not distribute |
Yup. |
Still broken. We made the implicit assumption that |
During npm update:
Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'ts-node' imported from /home/hex/ZweloProject/ClientApp/node_modules/maplibre-gl/
at new NodeError (node:internal/errors:371:5)
npm ERR! at packageResolve (node:internal/modules/esm/resolve:884:9)
npm ERR! at moduleResolve (node:internal/modules/esm/resolve:929:18)
npm ERR! at defaultResolve (node:internal/modules/esm/resolve:1044:11)
npm ERR! at ESMLoader.resolve (node:internal/modules/esm/loader:422:30)
npm ERR! at ESMLoader.getModuleJob (node:internal/modules/esm/loader:222:40)
npm ERR! at ESMLoader.import (node:internal/modules/esm/loader:276:22)
npm ERR! at initializeLoader (node:internal/process/esm_loader:74:49)
npm ERR! at loadESM (node:internal/process/esm_loader:87:11)
npm ERR! at runMainESM (node:internal/modules/run_main:47:21) {
npm ERR! code: 'ERR_MODULE_NOT_FOUND'
The text was updated successfully, but these errors were encountered: