pnp-webpack-plugin | Transparently adds support for Plug'n'Play to Webpack | Build Tool library

No. What Webpack ends up including is not something published or reported. Using react-scripts alone would seen hundreds of modules and versions being shipped in production. Any library you add on top just adds to that weight.

With tree shaking and build deps, you can't rely upon that requires at all. Some of those, like Jest or ESLint, are dev-only. They have no runtime. Others will. Some runtime deps will be shaken out too, so can't rely on just recognizing the lib.

To be able to build the project with react-native-maps and use_frameworks as described in the question I had to fork the react-native-maps library and replace

Google-Maps-iOS-Utils with Google_Maps_iOS_Utils in header imports in

lib/ios/AirGoogleMaps/AIRGoogleMap.m:

These things usually happens when I'm using VSCODE. Usually there are 3 things I do to Fix. If this config works for you in other projects it might be usefull.

1. Run the "Reload Window" in VSCODE, usually fix the problem for me
2. Delete the node_modules and reinstall de deps, I use yarn and it fixed the problem before
3. It might worth reacreate manually the .eslintrc . Maybe there's an update in CRA and things changed. Usually I start a new project and run eslint --init and start creating a new eslintrc

And it's cool to check if the eslint plugin is workin in your IDE.

obs : I woul'd post this as a comment, however I can't yet.

You're loading the image path dynamically, but in runtime and depending on your webpack config, your assets' paths in the bundle can be different from what's in your code.

Here's the default url-loader config in webpack for apps created by create-react-app:

You should use typescript eslint parser:

Elaborating my comment. You could do this

1. Clone the repo to your local file system.
2. Run the repo's build commands to generate a build. You'll need to see the building instructions from the repo itself. Usually available in README.md or CONTRIBUTING.md.
3. Then, use either use npm link or npm install to reference the locally built package.

This error occurs when you have a library listed as your dependency but it does not actually exist due to some reason.

Similar post: Link

Evidently preset-flow was not enough for babel to transpile a flow type defined within a JS file. When I added the following line to devDependencies in my package.json the build worked perfectly.