Arsharth/hydrogen-web
1
0
Fork 0
forked from mystiq/hydrogen-web
Code Issues Pull requests Projects Releases Packages Wiki Activity
hydrogen-web/scripts/sdk/base-manifest.json

20 lines
815 B
JSON
Raw Normal View History

run two vite builds for the sdk build, assets & js separately
2021-12-20 23:47:31 +05:30
{
Update base-manifest.json
2022-04-20 23:06:30 +05:30
"name": "@thirdroom/hydrogen-view-sdk",
add description
2021-12-22 21:07:53 +05:30
"description": "Embeddable matrix client library, including view components",
v0.0.11
2022-07-07 01:01:24 +05:30
"version": "0.0.11",
Avoid ERR_REQUIRE_ESM errors when requiring SDK
2022-04-06 04:47:14 +05:30
"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 12:42:00 +05:30
"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 03:49:13 +05:30
"./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 14:38:16 +05:30
"./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 12:42:00 +05:30
"./download-sandbox.html": "./asset-build/assets/download-sandbox.html",
"./assets/*": "./asset-build/assets/*"
Avoid ERR_REQUIRE_ESM errors when requiring SDK
2022-04-06 04:47:14 +05:30
}
run two vite builds for the sdk build, assets & js separately
2021-12-20 23:47:31 +05:30
}
Reference in a new issue Copy permalink