vector-im-hydrogen-web/scripts/sdk/base-manifest.json

{
    "name": "hydrogen-view-sdk",
    "description": "Embeddable matrix client library, including view components",
    "version": "0.0.9",
    "main": "./lib-build/hydrogen.cjs.js",
    "exports": {
        ".": {
            "import": "./lib-build/hydrogen.es.js",
            "require": "./lib-build/hydrogen.cjs.js"
        },
        "./paths/vite": "./paths/vite.js",
        "./style.css": "./asset-build/assets/index.css",
        "./main.js": "./asset-build/assets/main.js",
        "./download-sandbox.html": "./asset-build/assets/download-sandbox.html",
        "./assets/*": "./asset-build/assets/*"
    }
}
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",`
bump SDK version 2022-03-01 15:45:24 +01:00			`"version": "0.0.9",`
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",`
			`"./style.css": "./asset-build/assets/index.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			`}`