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
Observed in #1186 that GitHub actions had started failing all of a sudden
TypeError: Failed to parse URL from file://file:///Users/owenbuckley/Workspace/project-evergreen/greenwood/node_modules/lit-html/lit-html.js.map
at new Request (node:internal/deps/undici/undici:5272:19)
at NodeModulesResource.resolve (file:///Users/owenbuckley/Workspace/project-evergreen/greenwood/packages/cli/src/plugins/resource/plugin-node-modules.js:41:12)
... 5 lines matching cause stack trace ...
at async file:///Users/owenbuckley/Workspace/project-evergreen/greenwood/packages/cli/src/lifecycles/serve.js:42:37
at async file:///Users/owenbuckley/Workspace/project-evergreen/greenwood/packages/cli/src/lifecycles/serve.js:42:37
at async file:///Users/owenbuckley/Workspace/project-evergreen/greenwood/packages/cli/src/lifecycles/serve.js:42:37 {
[cause]: TypeError [ERR_INVALID_URL]: Invalid URL
at new NodeError (node:internal/errors:405:5)
at new URL (node:internal/url:676:13)
at new Request (node:internal/deps/undici/undici:5270:25)
at NodeModulesResource.resolve (file:///Users/owenbuckley/Workspace/project-evergreen/greenwood/packages/cli/src/plugins/resource/plugin-node-modules.js:41:12)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async file:///Users/owenbuckley/Workspace/project-evergreen/greenwood/packages/cli/src/lifecycles/serve.js:44:29
at async file:///Users/owenbuckley/Workspace/project-evergreen/greenwood/packages/cli/src/lifecycles/serve.js:42:37
at async file:///Users/owenbuckley/Workspace/project-evergreen/greenwood/packages/cli/src/lifecycles/serve.js:42:37
at async file:///Users/owenbuckley/Workspace/project-evergreen/greenwood/packages/cli/src/lifecycles/serve.js:42:37
at async file:///Users/owenbuckley/Workspace/project-evergreen/greenwood/packages/cli/src/lifecycles/serve.js:42:37 {
input: 'file://file:///Users/owenbuckley/Workspace/project-evergreen/greenwood/node_modules/lit-html/lit-html.js.map',
code: 'ERR_INVALID_URL'
}
}
Details
Upon further inspection of the issue, turns out is due to this code we had in place to leverage import.meta.resolve that is now activated when running on Node 18.19.0, which is when this feature is first getting introduced now. But clearly the implementation is broken 🤦♂️
There is a ticket I had tracking for integrating #684 in as many places as possible, and now fixing the original implementation, but will take a little bit of time. (I tried quickly seeing if I could get compat with import.meta.resolve but it was starting to go down a rabbit hole 🐰 )
I think the plan here will be to remove the import.meta.resolve code so we can at least ensure Greenwood can run properly, and we will refactor to use import.meta.resolve as we approach 1.0 release.
The text was updated successfully, but these errors were encountered:
Summary
Observed in #1186 that GitHub actions had started failing all of a sudden
Details
Upon further inspection of the issue, turns out is due to this code we had in place to leverage
import.meta.resolve
that is now activated when running on Node 18.19.0, which is when this feature is first getting introduced now. But clearly the implementation is broken 🤦♂️There is a ticket I had tracking for integrating #684 in as many places as possible, and now fixing the original implementation, but will take a little bit of time. (I tried quickly seeing if I could get compat with
import.meta.resolve
but it was starting to go down a rabbit hole 🐰 )I think the plan here will be to remove the
import.meta.resolve
code so we can at least ensure Greenwood can run properly, and we will refactor to useimport.meta.resolve
as we approach 1.0 release.The text was updated successfully, but these errors were encountered: