Remove src to lib rewrites on package.json files

[yamadapc]

This commit modifies the strategy to local src/lib rewrites, so that the package.json files are never modified.

Intead, the package.json files always point at bin/...; which in turn requires lib/bin.js.

During development, lib/bin.js can just require src/bin.js and rely on require.extensions register. But on distribution lib/** can be pre-built.

By maintaining a stable bin/... entry-point, the following benefits are achieved:

• The git workspace does not become dirty after a build
• It's not possible to get into a state where node_modules/.bin/parcel points at a non existant lib/ file, which can only be fixed by removing node_modules and yarn installing again

✔️ PR Todo

• Verify distributed assets from CI

[mattcompiles]

@yamadapc Is my understanding correct that to use Parcel via parcel link you'll now need to run yarn lerna run dev:prepare beforehand? Otherwise there won't be anything present in lib/bin.js?

[yamadapc]

@yamadapc Is my understanding correct that to use Parcel via parcel link you'll now need to run yarn lerna run dev:prepare beforehand? Otherwise there won't be anything present in lib/bin.js?

That's right. We could add a postinstall hook or such that runs dev:prepare on local.

But IMO this is better because before you also would get corrupted workspaces on builds linked or otherwise.

I have a feeling at the moment that you can run yarn build once and after that your workspace is unable to build itself again. Also there are those dirty files & yarn over a dirty workspace will break node_modules links forever so then you need to clean-up.

I'm running benchmarks in https://github.com/parcel-bundler/parcel-benchmark-action with prod. builds and in the current setup the workspace gets corrupted every time I build.

So this change would help; there also is no way to commit the dirty files.

The specific workflow for parcel-link might change very slightly; but it should be alright.