forked from mystiq/hydrogen-web
cd007b40e1
Fix https://github.com/vector-im/hydrogen-web/issues/686 Fix https://github.com/vector-im/hydrogen-web/issues/682 Instead of deleting the whole `target/` directory, leave it alone so the symlink driving the `npm link`/`yarn link` stays in tact. Leave Vite builds in their build directories (`/lib-build`/`/asset-build`) so you can `vite build --watch` to build on local changes and still have a consisent place to reference in the `package.json` `exports`. Previously, everything relied on `build.sh` which does a bunch of moving and renaming and made it hard to rebuild on changes. Add back support for CommonJS (adding the `package.json` `exports`). The last piece is making sure the `?url` imports (`import workerPath from 'hydrogen-view-sdk/main.js?url';`) work still. It looks like this may have just been solved via https://github.com/vitejs/vite/issues/6725 -> https://github.com/vitejs/vite/pull/7073 (literally 2 days ago) and we just need to wait for the next Vite release 🎉
17 lines
538 B
Bash
Executable file
17 lines
538 B
Bash
Executable file
#!/bin/bash
|
|
rm -rf target/*
|
|
yarn run vite build -c vite.sdk-assets-config.js
|
|
yarn run vite build -c vite.sdk-lib-config.js
|
|
yarn tsc -p tsconfig-declaration.json
|
|
./scripts/sdk/create-manifest.js ./target/package.json
|
|
mkdir target/paths
|
|
# this doesn't work, the ?url imports need to be in the consuming project, so disable for now
|
|
# ./scripts/sdk/transform-paths.js ./src/platform/web/sdk/paths/vite.js ./target/paths/vite.js
|
|
cp doc/SDK.md target/README.md
|
|
pushd target
|
|
pushd asset-build/assets
|
|
rm !(main).js *.wasm
|
|
popd
|
|
rm index.html
|
|
popd
|