mattermost/webapp
Harrison Healey dfdc0e28d0
MM-52536 Webpack unification part 2 (#23557)
* Remove unused bundle-loader

* Remove broken webpack-live-reload-plugin

* Remove unused terser-webpack-plugin

* Remove unused dotenv-webpack

* Update and share type definition for Webpack global values

* Share eslint-import-resolver-webpack

* Remove unused pmmmwh/react-refresh-webpack-plugin

* Remove webpack-cli/serve since it's already part of webpack-cli

* Remove unused Webpack packages from Components

* Share and update style-loader

* Remove unused image-webpack-loader from Boards
2023-06-12 11:50:34 -04:00
..
boards MM-52536 Webpack unification part 2 (#23557) 2023-06-12 11:50:34 -04:00
channels MM-52536 Webpack unification part 2 (#23557) 2023-06-12 11:50:34 -04:00
platform MM-52536 Webpack unification part 2 (#23557) 2023-06-12 11:50:34 -04:00
playbooks MM-52536 Webpack unification part 2 (#23557) 2023-06-12 11:50:34 -04:00
scripts MM-51729 Fix make dev after monorepo move (#22687) 2023-03-28 15:36:52 -04:00
.gitignore Run type check for all web app packages in CI (#22578) 2023-03-23 10:10:52 -04:00
.npmrc MM-52093 : Revert back the 'global-style' npmrc config (#22901) 2023-04-13 08:31:35 +05:30
config.mk Mono repo -> Master (#22553) 2023-03-22 17:22:27 -04:00
Makefile Fixed stop error on webapp makefile (#22662) 2023-04-10 11:44:00 -04:00
package-lock.json MM-52536 Webpack unification part 2 (#23557) 2023-06-12 11:50:34 -04:00
package.json MM-52536 Webpack unification part 2 (#23557) 2023-06-12 11:50:34 -04:00
README.md Fix references from 'packages/*' to 'platform/*' in READMEs (#23498) 2023-06-02 15:35:58 +05:30

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 boards) 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=boards

# 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.