hydrogen-web/scripts/sdk/build.sh

#!/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
Add hash-bang to fix build error 2021-12-27 15:51:25 +05:30			`#!/bin/bash`
Make the SDK friendly to locally link and develop on 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 🎉 2022-02-26 12:42:00 +05:30			`rm -rf target/*`
run two vite builds for the sdk build, assets & js separately 2021-12-20 23:47:31 +05:30			`yarn run vite build -c vite.sdk-assets-config.js`
			`yarn run vite build -c vite.sdk-lib-config.js`
somewhat works, but not everything we need it's missing still: - non-css assets like the download sandbox and the olm worker aren't written for some reason - the es and cjs lib.js entry points end up in assets with a hash for some reason - in these entry files, apart from our exports, something is adding an import statement for every import that was found in the tree - all assets are hashed even though the config tries to disable that - tests are included 2021-12-17 18:58:25 +05:30			`yarn tsc -p tsconfig-declaration.json`
			`./scripts/sdk/create-manifest.js ./target/package.json`
include path/vite in sdk bundle 2021-12-21 19:58:34 +05:30			`mkdir target/paths`
dont add paths/vite to sdk output, as it does not work 2022-01-12 23:01:55 +05:30			`# 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`
update SDK doc, use it as sdk package readme 2021-12-22 20:50:54 +05:30			`cp doc/SDK.md target/README.md`
move output of both lib and asset build around for coherent package 2021-12-21 16:54:33 +05:30			`pushd target`
			`pushd asset-build/assets`
Make the SDK friendly to locally link and develop on 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 🎉 2022-02-26 12:42:00 +05:30			`rm !(main).js *.wasm`
move output of both lib and asset build around for coherent package 2021-12-21 16:54:33 +05:30			`popd`
Make the SDK friendly to locally link and develop on 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 🎉 2022-02-26 12:42:00 +05:30			`rm index.html`
move output of both lib and asset build around for coherent package 2021-12-21 16:54:33 +05:30			`popd`