Hi @h1b9b! Thx for the PR, appreciated.

I do have time tomorrow to take a deeper look into it.

Did you check if the WebpackShellPlugin still works? (buildThreads => App) The last time I tested it, it broke (quite a while ago though).

It would not be a big deal in case the plugin does not support webpack v5. We don't really need the onBuildExit hook => we could move the docs resources copy logic "one level up" => into the buildThreads program.

I read somewhere, that chunk names inside magic comments get handled differently in v5.

e.g.:

        Neo.config.mainThreadAddons.forEach(addon => {
            if (addon !== 'AnalyticsByGoogle') {
                imports.push(import(/* webpackChunkName: 'src/main/addon/[request]' */ `./main/addon/${addon}.mjs`));
            }
        });

In v4 this only affected the (dist) dev env, in v5 i think it was for prod as well. Will double-check if the chunk paths are still reasonable.

Did you check if the dist versions of some examples or apps still work with the changes?

There is one override for the main thread in place:

https://github.com/neomjs/neo/blob/dev/src/Main.mjs#L195

        if (window.webpackJsonp) {
            __webpack_require__.p = Neo.config.basePath.substring(6);
        }

We need to verify that this one still works (not nice, but mandatory, since the main thread can get picked up from different levels inside the folder hierarchy).

Will ping you tomorrow!

Best regards, Tobias

Thanks for the tips, I went too fast for the upgrade yesterday. Sorry 🙏

Did you check if the WebpackShellPlugin still works? (buildThreads => App) The last time I tested it, it broke (quite a while ago though).

It would not be a big deal in case the plugin does not support webpack v5. We don't really need the onBuildExit hook => we could move the docs resources copy logic "one level up" => into the buildThreads program.

I went for a simple replacement solution. So I replaced WebpackShellPlugin with WebpackHookPlugin. Cause WebpackShellPlugin didn't get an update since 2017 and WebpackHookPlugin uses the new webpack hook API

I also upgraded css/post-css loaders and their usage to have full webpack 5 support

There is warning on html-webpack-plugin that is fixed in the alpha version so I pushed a commit updating it but it can be removed until the next release is available cause the build is still ok with the warning. It should be release soon (cf webpack 5 support issue)

There a problem with the chunk names. The apps are still working. But the chunks aren't split as before in the dev build and the indexes on the production build are different. So I put the PR in WIP until I figure out what's going on and fix it 😅

got time now to dive into your changes. will merge them first to get you into the contributors list.