Improving ESM and SvelteKit support

[lachlancollins]

Hi, my team have recently started using this package in our SvelteKit app, and I decided to look into the SvelteKit warning messages and complex instructions for what should be a simple import (e.g. #27).

At this point I have a strong suspicion this has to do with the rollup config and settings in the bundled package.json, but I've also noticed that the repo only contains the code to build the docs, not the npm package.

It's obviously a huge plus to have interactive docs, but I think this repo could benefit from a restructure to include the config to bundle and package the carousel, which could then be changed to improve the compatibility with the CJS/ESM ecosystems.

One way to go about this would be to use a monorepo structure (e.g. docs/ and package/ folders) with separate package.json files and separate dev/build commands. An alternative would be to use SvelteKit and its built-in packaging system (which is still experimental).

I think the simpler option would be just a monorepo. Please let me know your thoughts, I'm very happy to make a PR if you like this idea!