Skip to content

source location for journey files has incorrect filepath #520

@vigneshshanmugam

Description

@vigneshshanmugam
  • 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions