cd007b40e1
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 🎉
24 lines
705 B
JavaScript
Executable file
24 lines
705 B
JavaScript
Executable file
#!/usr/bin/env node
|
|
const fs = require("fs");
|
|
const appManifest = require("../../package.json");
|
|
const baseSDKManifest = require("./base-manifest.json");
|
|
/*
|
|
Need to leave typescript type definitions out until the
|
|
typescript conversion is complete and all imports in the d.ts files
|
|
exists.
|
|
```
|
|
"types": "types/lib.d.ts"
|
|
```
|
|
*/
|
|
const mergeOptions = require('merge-options');
|
|
|
|
const manifestExtension = {
|
|
devDependencies: undefined,
|
|
scripts: undefined,
|
|
};
|
|
|
|
const manifest = mergeOptions(appManifest, baseSDKManifest, manifestExtension);
|
|
const json = JSON.stringify(manifest, undefined, 2);
|
|
const outFile = process.argv[2];
|
|
fs.writeFileSync(outFile, json, {encoding: "utf8"});
|