Orphan (and maybe unneccessary) dependency zen-observable-ts has an invalid sourcemap
See original GitHub issueDescribe 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:
- Created 3 years ago
- Comments:11 (10 by maintainers)
Top GitHub Comments
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.
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