Files
zeekay c671872b0b The packages this repo publishes carry our scope
webapp/platform publishes six packages and the channels app carries a seventh
in-tree, and every one of them went out under @mattermost — types, client,
components, shared, eslint-plugin, compass-icons and mattermost-redux — while
the plugin that consumes them already asks for @hanzoteam/types and
@hanzoteam/client by name. It could not build: it was asking a registry for a
package nobody publishes.

They are @hanzoteam/* now, and mattermost-redux is @hanzoteam/redux, moved to
src/packages/@hanzoteam/redux so the directory matches the alias that always
pointed there.

@mattermost/calls-common and @mattermost/desktop-api stay. Those are published
by someone else and resolved from npm; renaming a package we merely consume
would name a thing that does not exist.

The jest moduleNameMapper entries needed doing by hand — they spell the scope
inside a regex, so a sweep over the plain name walks straight past them, and a
missed one fails at require time rather than at build.
2026-08-28 23:44:39 -07:00

39 lines
1.0 KiB
JSON

{
"compilerOptions": {
"allowJs": true,
"module": "commonjs",
"moduleResolution": "node",
"target": "ES2022",
"lib": [
"ES2022"
],
"declaration": true,
"strict": true,
"resolveJsonModule": true,
"isolatedModules": true,
"esModuleInterop": true,
"allowSyntheticDefaultImports": true,
"jsx": "react",
"preserveConstEnums": true,
"outDir": "./lib",
"rootDir": "../../channels/src/packages/@hanzoteam/redux/src",
"composite": true,
"useUnknownInCatchVariables": false,
"skipLibCheck": true,
"tsBuildInfoFile": "tsconfig.tsbuildinfo",
"paths": {
"@hanzoteam/redux/*": ["../../channels/src/packages/@hanzoteam/redux/src/*"]
}
},
"include": [
"../../channels/src/packages/@hanzoteam/redux/src/**/*"
],
"exclude": [
"../../**/*.test.*"
],
"references": [
{"path": "../types"},
{"path": "../client"}
]
}