Turfjs / Turfjs/turf

source map error

Open
#3,047 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
10.5k
Forks
1k
Avg merge
1h 11m
Merged PRs (30d)
4

Description

After updating to version 7.3.4 we get the following error:

Creating an optimized production build...
Compiled with warnings.

Failed to parse source map from '..\node_modules\arc\src\arc.ts' file: Error: ENOENT: no such file or directory, open '..\node_modules\arc\src\arc.ts'

Failed to parse source map from '\node_modules\arc\src\coord.ts' file: Error: ENOENT: no such file or directory, open '\node_modules\arc\src\coord.ts'

Failed to parse source map from '\node_modules\arc\src\great-circle.ts' file: Error: ENOENT: no such file or directory, open '\node_modules\arc\src\great-circle.ts'

Failed to parse source map from '\node_modules\arc\src\index.ts' file: Error: ENOENT: no such file or directory, open '\node_modules\arc\src\index.ts'

Failed to parse source map from '\node_modules\arc\src\line-string.ts' file: Error: ENOENT: no such file or directory, open '\node_modules\arc\src\line-string.ts'

Failed to parse source map from '\node_modules\arc\src\utils.ts' file: Error: ENOENT: no such file or directory, open '\node_modules\arc\src\utils.ts'

does not effect functionality but still thought to report it. thanks

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the optimized production build on version 7.3.4 and inspect the source-map references for node_modules/arc/src/arc.ts, coord.ts, great-circle.ts, index.ts, line-string.ts, and utils.ts. Trace how those references are packaged, then verify that the build completes without the reported missing-file warnings.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.