You've already forked matrix-js-sdk
mirror of
https://github.com/matrix-org/matrix-js-sdk.git
synced 2025-08-09 10:22:46 +03:00
* Rename `switch_package_to_release.js` to `.cjs` Slightly surprisingly, the symlink is enough to make `node switch_package_to_release.js` work. * Rename .eslintrc.js to .cjs Again, declare this as commonjs * Move `type:module` declaration into package.json. matrix-js-sdk is built into ECMAScript modules, and we should declare it as such. See https://nodejs.org/api/packages.html#type. Failure to do so causes problems for javascript projects attempting to build against matrix-js-sdk: see https://github.com/matrix-org/matrix-js-sdk/issues/4347. Previously, we did this as part of the package.json switcheroo, but that is unnecessarily fragile. matrix-react-sdk, element-web, etc are unaffected by this, because they use the typescript files directly, by importing `matrix-js-sdk/src/...`.
15 lines
600 B
Bash
Executable File
15 lines
600 B
Bash
Executable File
#!/bin/bash
|
|
|
|
# For the published and dist versions of the package,
|
|
# we copy the `matrix_lib_main` and `matrix_lib_typings` fields to `main` and `typings` (if they exist).
|
|
# This small bit of gymnastics allows us to use the TypeScript source directly for development without
|
|
# needing to build before linting or testing.
|
|
|
|
for i in main typings browser
|
|
do
|
|
lib_value=$(jq -r ".matrix_lib_$i" package.json)
|
|
if [ "$lib_value" != "null" ]; then
|
|
jq ".$i = .matrix_lib_$i" package.json > package.json.new && mv package.json.new package.json && yarn prettier --write package.json
|
|
fi
|
|
done
|