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
To extract the source location information for journeys, we rely on source-map library to extract the fileName and other stack related information. But there was a bug in the library that did not handle the absolute file paths correctly when extracting that info which lead to incorrect fileName and resulted in push command getting failed.
Error: Build failed with 1 error:
error: ENOENT: no such file or directory, open '/Users/vigneshh/elastic/synthetics/examples/todos/file:/Users/vigneshh/elastic/synthetics/examples/todos/basic.journey.ts'
at failureErrorWithLog
....
errors: [
{
detail: [Error],
location: null,
notes: [Array],
pluginName: 'esbuild-multiasset-plugin',
text: "ENOENT: no such file or directory, open '/Users/vigneshh/elastic/synthetics/examples/todos/file:/Users/vigneshh/elastic/synthetics/examples/todos/basic.journey.ts'"
}
],
warnings: []
}
But there is a fix in the latest version that handles the file urls correctly and also has better ESM support - cspotcode/node-source-map-support#38
The text was updated successfully, but these errors were encountered:
But there is a fix in the latest version that handles the file urls correctly and also has better ESM support - cspotcode/node-source-map-support#38
The text was updated successfully, but these errors were encountered: