Remove src directory and already-bundled dependencies from published package

[1000hz]

We currently include the src directory in the published artifact, resulting in an extra 2.6 MB on disk.

Additionally, although we bundle the application into wrangler-dist/cli.js, we publish package.json still declaring dependencies on those bundled libraries, resulting in an additional 32 MB of packages getting installed even though they've already been included in the bundle.

In order to minimize installation time of wrangler, we should consider removing src from the published artifact and either moving bundled dependencies to devDependencies or publishing with a stripped down package.json that only includes within dependencies any externalized modules. This becomes more important as we start depending on larger external modules (e.g. workerd) and need to keep time-to-install within reasonable bounds.

[1000hz]

On further inspection, it turns out we mostly already do only include externalized dependencies within our dependencies array. The only bundled dependencies we're unnecessarily installing seem to be nanoid and xxhash-wasm, which we should still move into devDependencies, though doing so will net us far less savings than I was hoping for (~250 KB on disk).

On the bright side, we're already doing the right thing, so GO TEAM! 🥳

Sorry for the false alarm, and h/t @petebacondarwin for calling attention to the quick savings we could gain by removing src.

[petebacondarwin]

I think xxhash-wasm is still needed as a dependency for now. It is used to create a hash key for "Workers Sites" uploads. But once we move over to Pages based asset uploads, this can go.

[1000hz]

oh, good to know! I just meant xxhash-wasm is currently bundled, not externalized, so we can move it over to devDependencies.

[petebacondarwin]

Thanks @1000hz for enlightening me about how xxhash-wasm has the WASM module inlined in the JS module! So indeed it is already bundled.

[GregBrimble]

If we ship the JS API and want to provide declarationMaps, we'd probably want to include the src directory in the published package.

I'm a pretty big +1 to doing this! It can make using a package so much easier.

[mrbbot]

Closed by #3191