mirrors/vector-im-hydrogen-web
1
0
Fork 0
mirror of https://github.com/vector-im/hydrogen-web.git synced 2024-12-23 03:25:12 +01:00
Code Issues Projects Releases Wiki Activity
e5b87a8518
vector-im-hydrogen-web/scripts/sdk/base-manifest.json

20 lines
803 B
JSON
Raw Normal View History

run two vite builds for the sdk build, assets & js separately
2021-12-20 19:17:31 +01:00
{
change sdk package name to hydrogen-view-sdk as we might want to also have a lower level sdk later on
2021-12-22 15:56:21 +01:00
"name": "hydrogen-view-sdk",
add description
2021-12-22 16:37:53 +01:00
"description": "Embeddable matrix client library, including view components",
Changes for sdk release
2023-10-08 19:54:49 +02:00
"version": "0.1.7",
Avoid ERR_REQUIRE_ESM errors when requiring SDK
2022-04-06 01:17:14 +02:00
"main": "./lib-build/hydrogen.cjs.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
"exports": {
".": {
"import": "./lib-build/hydrogen.es.js",
"require": "./lib-build/hydrogen.cjs.js"
},
"./paths/vite": "./paths/vite.js",
Merge branch 'master' into madlittlemods/686-682-local-friendly-development-and-commonjs Conflicts: package.json scripts/sdk/base-manifest.json scripts/sdk/build.sh
2022-04-20 00:19:13 +02:00
"./style.css": "./asset-build/assets/theme-element-light.css",
"./theme-element-light.css": "./asset-build/assets/theme-element-light.css",
"./theme-element-dark.css": "./asset-build/assets/theme-element-dark.css",
Fix typos pointing to wrong files
2022-02-26 10:08:16 +01:00
"./main.js": "./asset-build/assets/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
"./download-sandbox.html": "./asset-build/assets/download-sandbox.html",
"./assets/*": "./asset-build/assets/*"
Avoid ERR_REQUIRE_ESM errors when requiring SDK
2022-04-06 01:17:14 +02:00
}
run two vite builds for the sdk build, assets & js separately
2021-12-20 19:17:31 +01:00
}
Reference in New Issue Copy Permalink