Small library size & building from fork

[jacksongoode]

In an effort to make the library smaller by avoiding building in any nodes or utilities that I'm not using my project, I went through and commented out a handful of paths that didn't need to be in the final bundle. The result was a wasm bundle about half the size.

However, I'm struggling to figure out how to install the modified library if I fork the project. It seems like I can build the Wasm bundle, but then inserting it into the resultant index.js and a build is what I'm a little bit confused around. I thought a postinstall script might be able to do it but I thought I would have seen some clarity on how the final dist was formed. Here's my branch so you can see the minimal changes I made. I imagine I'm missing something simple.

[nick-thompson]

Hey @jacksongoode great question.

The result was a wasm bundle about half the size.

Woah! That's great.

Your changes look good. If you're having trouble building, take a look at the npm run wasm script in the web/offline-renderer js packages: https://github.com/elemaudio/elementary/blob/main/js/packages/web-renderer/package.json#L37. From within the web-renderer package you should be able to just run npm run wasm && npm run build and arrive at a ready-to-go dist folder containing your slimmed down build.

From that point you should be able to import it into your project the same as you do with the official @elemaudio/web-renderer package. You'll just have to find a way to distribute the custom dist folder to your project– e.g. you could use npm link for local development. For production you could publish to your own npm package or just copy/paste the dist folder into your project's work tree.

Let me know if that helps