Files
zeekayandHanzo Dev 65d285cc8e Ask npm for the icon package by the name npm has
compass-icons is published by Mattermost and consumed from the registry; this
tree contains no source for it and webapp/platform has no such workspace. Under
our scope npm has nothing to fetch:

  404 Not Found - GET https://registry.npmjs.org/@hanzoteam/compass-icons/-/compass-icons-0.1.61.tgz

The lockfile is the proof of what it is. Its integrity for the renamed entry is
sha512-Xq7QHyxq7NPljgqlzwRp6tWGe5s…, byte for byte the integrity npm publishes
for @mattermost/[email protected] — one tarball, filed under a name nobody
serves. The install then succeeds on any machine whose npm cache already holds
that tarball, because a cache hit by integrity never asks the registry, and
fails on every clean one. That is the whole distance between a developer's box
and a build node: `npm ci --cache <fresh dir>` fails on master and passes here.

Same rule the scope change already applied to calls-common and desktop-api:
a package we merely consume keeps the name its publisher gave it.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-08 13:22:37 -07:00
..

Mattermost Components

The goal of this package is to be a place where components common to all products can be shared.

Currently a work in progress. Next steps involve implementing webpack module federation in the webapp and locking down how the development experience will work for the webapp multi product architecture.

Usage

Coming soon with multi product architecture.

Compilation

Building is done using rollup. This must be done so the webapp webpack will pick up the changes. (multi product development experience coming soon)

npm run build

or from the root of the webapp with

npm run build --workspace=platform/components