vector-im-hydrogen-web/scripts/sdk/build.sh

#!/bin/bash
# Exit whenever one of the commands fail with a non-zero exit code
set -e
set -o pipefail
# Enable extended globs so we can use the `!(filename)` glob syntax
shopt -s extglob

# Only remove the directory contents instead of the whole directory to maintain
# the `npm link`/`yarn link` symlink
rm -rf target/*
yarn run vite build -c vite.sdk-assets-config.js --mode sdk
yarn run vite build -c vite.sdk-lib-config.js --mode sdk
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
cp doc/SDK-CHANGELOG.md target/CHANGELOG.md
pushd target/asset-build
rm index.html
popd
pushd target/asset-build/assets
# Remove all `*.wasm` and `*.js` files except for `main.js`
rm !(main).js *.wasm
popd
Add hash-bang to fix build error 2021-12-27 11:21:25 +01:00			`#!/bin/bash`
Fix asset build throwing and swallowing errors (#721) - Fix `svg-colorizer` throwing errors with Windows file paths - Fix `css-url-parser` swallowing errors because it was `async` - Fail SDK build script (`yarn build:sdk`, `build.sh`) overall when some commands are failing 2022-04-20 18:55:48 +02:00			`# Exit whenever one of the commands fail with a non-zero exit code`
			`set -e`
			`set -o pipefail`
Enable extended globs for removing all but some filename !(filename) See https://github.com/vector-im/hydrogen-web/pull/693#discussion_r853534719 2022-04-20 00:28:09 +02:00			# Enable extended globs so we can use the `!(filename)` glob syntax
			`shopt -s extglob`

Add some comments 2022-05-06 00:57:25 +02:00			`# Only remove the directory contents instead of the whole directory to maintain`
			# the `npm link`/`yarn link` symlink
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 08:12:00 +01:00			`rm -rf target/*`
Make service worker work with sdk 2024-08-16 12:03:39 +02:00			`yarn run vite build -c vite.sdk-assets-config.js --mode sdk`
			`yarn run vite build -c vite.sdk-lib-config.js --mode sdk`
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 14:28:25 +01:00			`yarn tsc -p tsconfig-declaration.json`
			`./scripts/sdk/create-manifest.js ./target/package.json`
include path/vite in sdk bundle 2021-12-21 15:28:34 +01:00			`mkdir target/paths`
dont add paths/vite to sdk output, as it does not work 2022-01-12 18:31:55 +01:00			`# 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 16:20:54 +01:00			`cp doc/SDK.md target/README.md`
Add Changelog for SDK 2023-05-11 14:43:09 +02:00			`cp doc/SDK-CHANGELOG.md target/CHANGELOG.md`
Clean up index.html in the right spot 2022-05-18 07:21:56 +02:00			`pushd target/asset-build`
			`rm index.html`
			`popd`
			`pushd target/asset-build/assets`
Explain what is being deleted by the strange syntax See https://github.com/vector-im/hydrogen-web/pull/693#discussion_r815284713 2022-04-20 18:59:49 +02:00			# Remove all `.wasm` and `.js` files except for `main.js`
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 08:12:00 +01:00			`rm !(main).js *.wasm`
move output of both lib and asset build around for coherent package 2021-12-21 12:24:33 +01:00			`popd`