mattermost/webapp
Harrison Healey 8b164711a4
MM-63138 Fix some console warnings (#30209)
* Fix forwardRef propTypes console error

The console error that was fixed by this is:
"Warning: forwardRef render functions do not support propTypes or defaultProps. Did you accidentally pass a React component?"

* Fix function component ref console error

This fixes the following error:
Warning: Function components cannot be given refs. Attempts to access this ref will fail. Did you mean to use React. forwardRef ()?
2025-02-14 16:21:52 -05:00
..
channels MM-63138 Fix some console warnings (#30209) 2025-02-14 16:21:52 -05:00
patches Patch eslint-plugin-react-hooks to properly handle class properties (#26493) 2024-03-18 14:24:15 -04:00
platform MM-62548: CPA Reordering - drag and drop (#30097) 2025-02-13 17:09:35 -06:00
scripts Add type annotation to generated language files map (#29283) 2024-11-15 14:19:40 -04:00
.gitignore Re-add package target to web app Makefile (#23960) 2023-07-11 11:58:29 +05:30
.npmrc Disable legacy-peer-deps and manually override mismatched dependencies (#27677) 2024-07-18 15:36:02 -04:00
config.mk Mono repo -> Master (#22553) 2023-03-22 17:22:27 -04:00
Makefile fix(webapp/Makefile): Drop quotes around appended cppflags (#27374) 2024-06-18 15:56:45 -04:00
package-lock.json [MM-62864] Bump katex to 0.16.21 (#30095) 2025-02-11 11:18:01 +05:30
package.json Add typescript-eslint-language-service (#30015) 2025-02-04 15:29:29 -07:00
README.md Prevent boards product from being included automatically (#23539) 2023-06-12 18:51:43 +02:00

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.