Comment by Sebastian on "Adding an external loader for React and ReactDOM in webpack"

CommentAdding an external loader for React and ReactDOM in webpack

Sebastian

May 15, 2018

Currently your JavaScript files are processed by Babel. If you want to use your loader for react the you have to identify the react files ideally by extension or specific file name pattern ( the test property is a regex field).

So basically paste your loader configuration below the current JS file rule and may delete the jsx extension above and use it with your loader.

But what’s the purpose of that loader? I couldn’t figure it out on a quick overview.

Marvin Dick

May 15, 2018

I have a main page that loads several React Apps via Ajax, the loader is supposed to use the CDNs for React and ReactDOM I specified on my main page so it doesn't loads those four times for each app. At the same time it's also supposed to tell the app NOT to use externals when they're tested in isolation. I was mainly following this guide:

medium.com/@rchaves/building-microfrontends-part-iv-using-cdns-tech-radar-for-consensus-7dd658c1edb7

But I'm guessing the webpack version in there is outdated, as my config looks pretty different.

Sebastian

May 15, 2018

I see.

Your config looks like it comes from a boilerplate template like create-react-app.

I use code splitting to diff my code from vendor libs via whitelist in the Webpack config (Webpack v3) or implicit via import statements (Webpack v4)

My have a look. May it come handy for your requirements.

github.com/HerrVoennchen/sample-project

Search Hashnode