John Pangalos

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...

Looking through the code for react-virutalized, it seems to only happen for default imports of types. Reference: https://github.com/bvaughn/react-virtualized/blob/master/source/WindowScroller/utils/onScroll.js @mewhhaha

Seems to actually just with files that don't have react components in them.

I was able to fix it by passing the react-redux context into the connected react router like this: ``` {/* your routes here /*} ``` Not sure why...

It could be because you need a Cargo.toml file. I was trying this then tried VSCode. Got that error, went back and added one and then things work. A Cargo.toml...

I also had a similar problem with pnpm (though not with pnp enabled) in that ale resolves eslint but doesn't respect the eslintignore. I fixed it by putting the ignore...

I have this problem as well though my work around is this: ```vim autocmd BufWritePre *.md,*.js,*.jsx,*.mjs,*.ts,*.tsx,*.css,*.less,*.scss,*.json,*.graphql,*.vue,*.yaml,*.html silent! PrettierAsync ``` Not the nicest thing, but it stops this error.

As for webpack, take a look a this (I believe it makes the sucrase website.) https://github.com/alangpierce/sucrase/blob/4163973a06fa9f4ac9a2d6b9cc0f04b343fe643d/website/config/webpack.config.dev.js

Is there anyway we could add these requirements to the Readme? Might save people some time.

You could do this using your native data storage. There should be a link to it in the Acl object. I used mongo db so yours is probably different. Also...