Bogus import in generated dist ESM file
See original GitHub issueBug Report
https://unpkg.com/browse/react-virtualized@9.22.3/dist/es/WindowScroller/utils/onScroll.js
What is the current behavior?
Last line of the linked file has the following bogus import pointing to a non-existent export:
import { bpfrpt_proptype_WindowScroller } from "../WindowScroller.js";
What is the expected behavior?
This import shouldn’t exist.
Which versions of React and react-virtualized, and which browser / OS are affected by this issue? Did this work in previous versions of react-virtualized?
Not sure which version this started shipping - but this import breaks when imported in native browser ESM and also breaks in strict bundlers like esbuild / rollup.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:76
- Comments:23 (1 by maintainers)
Top Results From Across the Web
Transpiling Typescript into double packages (CommonJS + ...
To do this, we set up the transpiler to generate esm and commonJS modules. In our situation, we can import a package from...
Read more >Rollup ESM generates broken imports - Stack Overflow
I had a similar issue (though with stream module, not http ), and for me the solution was to set browser: true in...
Read more >ECMAScript Modules - webpack
Imports in ESM are resolved more strictly. Relative requests must include a filename and file extension (e.g. *.js or *.mjs ) unless you...
Read more >Build Targets - Vue CLI
dist /myLib.css : Extracted CSS file (can be forced into inlined by setting css: { extract: false } in vue.config.js ). WARNING.
Read more >Options - Babel.js
npx babel --root-mode upward file.js # equivalent of passing the rootMode config ... code: false, }); // Minify the file in a second...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@bvaughn can we remove that bogus import please?
I have published a version of the package with the fix, you can use it via resolutions field in package.json