Skip to content
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

Update source-map dependency #2

Merged
merged 1 commit into from
Oct 8, 2019
Merged

Update source-map dependency #2

merged 1 commit into from
Oct 8, 2019

Conversation

jacobg213
Copy link
Contributor

Firstly thanks very much for this excellent library.

Problem

I am running a Nodejs app and am hitting the following error when using this library:

You must provide the URL of lib/mappings.wasm by calling SourceMapConsumer.initialize({ 'lib/mappings.wasm': ... }) before using SourceMapConsumer

Diagnosis

  • A dependency of yours "source-map" detects the runtime (Nodejs vs browser) in a broken way. That library then throws an exception if some client-side-specific code is not run.
  • The "check" checks for the presence of a variable "fetch" and the reasonable thinking is that only browsers will have fetch. The issue is that in my case and in some others (see here) 3rd party libraries can define a variable "fetch" which triggers the described error.

Tests

None

Firstly thanks very much for this excellent library.

I am running a Nodejs app and am hitting the following error when using this library:
```
You must provide the URL of lib/mappings.wasm by calling SourceMapConsumer.initialize({ 'lib/mappings.wasm': ... }) before using SourceMapConsumer
```

* A dependency of yours "source-map" detects the runtime (Nodejs vs browser) in a broken way. That library then throws an exception if some client-side-specific code is not run.
* The "check" checks for the presence of a variable "fetch" and the reasonable thinking is that only browsers will have fetch. The issue is that in my case and in some others (see [here](mozilla/source-map#349)) 3rd party libraries can define a variable "fetch" which triggers the described error.

None
@coveralls
Copy link

coveralls commented Oct 3, 2019

Pull Request Test Coverage Report for Build 14

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+5.7%) to 73.585%

Totals Coverage Status
Change from base Build 13: 5.7%
Covered Lines: 28
Relevant Lines: 37

💛 - Coveralls

@gajus gajus merged commit fe10d27 into gajus:master Oct 8, 2019
@jacobg213 jacobg213 deleted the patch-1 branch October 8, 2019 07:43
@github-actions
Copy link

🎉 This PR is included in version 3.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants