question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Orphan (and maybe unneccessary) dependency zen-observable-ts has an invalid sourcemap

See original GitHub issue

Describe the bug One of the aws-amplify dependencies, zen-obsevable-ts, has an invalid sourcemap. Here’s the first line of its sourcemap:

{"version":3,"file":"bundle.esm.js","sources":["../src/zenObservable.ts"]

This package didn’t publish its source code to NPM, so the link to ../src/zenObservable.ts will cause build-time warnings for some tools like source-map-loader.

Normally I’d just file a bug against the zen-obsevable-ts repo, but it’s archived. Normally for archived repos, I’d file a PR to Amplify to switch to the new, non-archived repo. But zen-obsevable-ts doesn’t seem to have any successor repo.

So I’m filing a bug report here because this repo is probably the only place to fix the problem.

Looking at https://unpkg.com/zen-observable-ts, there’s no executable code; the zen-observable-ts package seems to be solely a TS wrapper to add types around zen-observable. Here’s the entire ESM implementation:

import zenObservable from 'zen-observable';

var Observable = zenObservable;

export default Observable;
export { Observable };
//# sourceMappingURL=bundle.esm.js.map

So it might be possible to remove this package completely and just rely on zen-observable and @types/zen-observable.

I’m removing the rest of the bug report template since it doesn’t seem to apply to this case, but let me know if I should put it back.

I’ll take a stab at PR-ing a fix to this by removing this package and relying on @types/zen-observable instead.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:11 (10 by maintainers)

github_iconTop GitHub Comments

1reaction
nickarochocommented, May 20, 2021

Thanks for the insight and historical context. I need a little more time to fully understand what kind of scope this will take to resolve, so we appreciate your patience while we sort through it.

0reactions
stocaarocommented, Aug 9, 2022

Thats what I’m seeing. If you see anything different than that, happy to have this reopened with detail on what I’m missing. Thanks! Aaron

Read more comments on GitHub >

github_iconTop Results From Across the Web

CSS error source-map information is not available at URL ...
I am having a problem when I execute NPM ...
Read more >
source-map-explorer - npm
Analyze and debug space usage through source maps. Latest version: 2.5.3, last published: 3 months ago. Start using source-map-explorer in ...
Read more >
source-map-loader - webpack
This loader is especially useful when using 3rd-party libraries having their own source maps. If not extracted and processed into the source map...
Read more >
Sourcemap | Leader in Supply Chain Transparency & Due ...
Full suite end-to-end supply chain management software for resilience, compliance, and sustainability.
Read more >
Source map errors — Firefox Source Docs documentation
The error tells us that the source map is not JSON data — so we're serving the wrong file. There are a few...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found