6af8c2f83e
* Fix multiple copies of utility classes being loaded by the app When using SASS's at-import rule for a file containing CSS classes, the entirity of the imported file is included into that chunk of the JS bundle. This leads to those class definitions being duplicated multiple times in the code loaded by the browser. That doesn't happen for mixins, functions, or SASS variables which are evaluated at compile time. To prevent those classes from being repeatedly defined, we need to not import them into multiple bundles. We already load the utility classes into the root bundle, so we just need to make sure not to import sass/utils/_module.scss, sass/utils/_flex.scss, sass/utils/_animations.scss, or sass/utils/_modifiers.scss into any CSS files which are imported into individual components. * Canonize import paths for SCSS mixins and functions We previously imported some .scss files as `src/sass/...` and others as `sass/...`. This was allowed becuase sass-loader's `sassOptions.includePaths` included both `src` and `src/sass`. I've made that more consistent now and removed the redundant include path.
Mattermost Web App
This folder contains the client code for the Mattermost web app. It's broken up into multiple packages each of which either contains an area of the app (such as playbooks) or shared logic used across other packages (such as the packages located in the platform directory). For anyone who's used to working in the mattermost/mattermost-webapp repo, most of that is now located in channels.
npm Workspaces
To interact with a workspace using npm, such as to add a dependency or run a script, use the --workspace (or --workspaces) flag. This can be done when using built-in npm commands such as npm add or when running scripts. Those commands should be run from this directory.
# Add a dependency to a single package
npm add react --workspace=playbooks
# Build multiple packages
npm run build --workspace=platform/client --workspace=platform/components
# Test all workspaces
npm test --workspaces
# Clean all workspaces that have a clean script defined
npm run clean --workspaces --if-present
To install dependencies for a workspace, simply run npm install from this folder as you would do normally. Most packages' dependencies will be included in the root node_modules, and all packages' dependencies will appear in the package-lock.json. A node_modules will only be created inside a package if one of its dependencies conflicts with that of another package.
Useful Links
- Developer setup, now included with the Mattermost server developer setup
- Web app developer documentation