-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Perform escape analysis on imported types #206
Comments
Hey, thought I'd follow up on this as more things are starting to use esbuild which is incompatible with this behavior. Resulting in anyone using react-virtualized not being able to use some of the more modern tooling. Some effect tools: esbuild, vite, and snowpack. I would love to help in anyway I can including writing code. But I am not sure how to go about this. |
Looking through the code for react-virutalized, it seems to only happen for default imports of types. |
Seems to actually just with files that don't have react components in them. |
Reference: react-virtualized issue
This import appears in a source file which doesn't define components or composite types.
This line is in the output:
As
bpfrpt_proptype_WindowScroller
is never referred to, the binding and import can be cleaned up.The text was updated successfully, but these errors were encountered: