multicompiler | based compiler to create artificial software diversity | Compiler library

Well, I think there is a conflict in your dependence that is causing the errors. Remove every dependence in your package.json except vuepress, reinstall all dependencies and the error disappears. I'm not familiar with this, but I think it may be a problem with the versioning of core-js, vuepress is still using 2.x and you are using 3.x

The other problem with migrating to vuepress 1.2.0 is that some of the official plugins are not shipped with vuepress by default. So you need to manually install vuepress-plugin-pwa to use it. Check out the document for more detail.

BTW, I notice that you have both package-lock.json and yarn.lock in your repo, so I'm not sure which tool are you using. Currently, yarn is the recommended way, because npm could cause some errors in certain circumstances.

TS skipLibCheck compiler option could help

Awesome we figured this out.
So the answer was just version problems. The recent change to webpack 4 makes this quite cumbersome. 4 is not quite stable but if you use 3 you have to check every package, because most of the ones who support 4 are not backward compatible.

As for why you are having issues running webpack locally, I don't know. But I also don't use Windows.
You should try to find a solution for this though, versioning gets way harder if you have to do it globally once you start having more than one project.

This is likely to be a file generated by a webpack plugin (https://github.com/danethurber/webpack-manifest-plugin) after building the client-side bundle, that file name is hashed and necessary to the server so it knows how to render the base template which will then bootstrap the client.

Of course that's a guess since we don't have access to your json file, webpack configuration or package.json..

This repository uses a similar approach: https://github.com/CheesecakeLabs/react-redux-boilerplate/ It builds the client, generates the same kind of file and then builds the server bundle using that JSON file as information point to understand how the client bundle is named.

The JSON file should be similar to this:

If your webpack.config.js is a function, you can call it on your own to resolve to an object.

If you have several configs (you mentioned webpack.base.js and webpack.development.js) you can use Webpack Merge to just combine your options to a single object, and then write it to the file system.

I would recommend you to have an own script in package.json to do this job, which you can then always call after your webpack job:

Maybe it has something to do with your webpack.config file? Do you have the hot stuff setup in your entry?