David Welling

Try putting this in your global setup: ``` // jsDom does not implement offset* methods (they return 0). // This will break tests for components that // use react-virtualized-auto-sizer //...

If no `export default` is found, instead could you create `import * as moduleNameHold from './moduleName.js';` `export const moduleName = moduleNameHold;` ?

Also, it seems like the problem is confined to the SourceMapDevToolPlugin because setting devtool === 'eval' (which I think uses [EvalSourceMapDevToolPlugin](https://webpack.js.org/plugins/eval-source-map-dev-tool-plugin/)) seems to fix the problem. You just get really...

Hopefully the react-native code itself won't come into play. It seems like the "type": "module" setting only applies to the code contained in the module defined by the package.json. The...

Unfortunately, I don't know the correct way to do that. I've been looking through the metro-react-native-babel-preset and I found an option for `disableImportExportTransform` which seems to avoid adding the "@babel/plugin-transform-modules-commonjs"....

It's looking pretty encouraging so far. If I disable `hmr`, I am able to get our app to load with the disableImportExportTransform option. For you or anybody that happens to...

This is working pretty well for me if drop HMR. I noticed that you put the enhancement label on. I won't close it if you are planning to enhance the...

This is great news. We finally just made it to v2.5.2 so it might take us a little while to get on 3.x. I took a look at https://github.com/callstack/repack/blob/v3/packages/repack/src/modules/WebpackHMRClient.ts and...

I know in v1 my initial bundles worked fine, but I had to turn off HMR. I assumed it was because module.hot was causing webpack to use require inside the...

One other data point, I inconsistently get something like this: ``` x [18:01:24.796Z][DevServer@android] Failed to symbolicate { error: 'Start offset -1590986392 is outside the bounds of the buffer' } !...