Open michaelwarren1106 opened 1 year ago
IIRC, those weird bracketed source paths are placed there by Closure to represent its injected polyfills. I was messing around with updating some dependencies a while ago and I believe a newer version of Closure fixed this.
Do we think this is fixed now? I replaced Gulp with a direct call to Closure and noticed that the sourcemaps are slightly different.
i haven’t seen an error in a long time, and we’ve dumped create-react-app like the rest of the react world has, so i’d call it good for now and re-open if something else comes up?
Description
In a stock, non-ejected,
create-react-app
scaffolded application, using the@webcomponents/scoped-custom-element-registry
polyfill package results in sourcemap warnings during the build step potentially caused by the sourcemaps being malformed?Example
The warning produce is similar to:
The beginning of the generated sourcemap for the polyfill is:
Steps to reproduce
create-react-app
application with Typescript@webcomponents/scoped-custom-element-registry/
npm run build
Expected behavior
No warnings are shown
Actual behavior
Warning above is shown
Version
@webcomponents/scoped-custom-element-registry@0.0.5