Initially when ProxyPack was first setup, it was more a POC, and didn't really have a good design. With this refactor it has a more solid design that will be easier to extend and fix.
The source folder is now divided along the entry points to the application, a cli, webpack, a browser. And then also another folder for the server. They all talk to the server. The server has also been cleaned up and moved off of a class, to isolate things.
only one breaking change renaming mappings to webpackMappings
Webpack is now resolved through the context output path rather than copying files from the compiler every time, this means less memory is used up, since we are not copying the source files into memory
test coverage is now ....
externalMappings were very unstable before, in this PR we've added a monitor lib to monitor externalMappings, and update the source code when a change is detected
Initially when ProxyPack was first setup, it was more a POC, and didn't really have a good design. With this refactor it has a more solid design that will be easier to extend and fix.
The source folder is now divided along the entry points to the application, a cli, webpack, a browser. And then also another folder for the server. They all talk to the server. The server has also been cleaned up and moved off of a class, to isolate things.
mappingstowebpackMappings