You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Set up an NPM toolchain that can take react, redux, material-ui, and router then output NPM library files. These files should be ready to be deployed as an NPM package by running a script command such as npm run build-library
The components should be tested to work on other react libraries. This can be done using npm link <library name>
The text was updated successfully, but these errors were encountered:
The material-ui issue was being caused by a known issue during the local testing process. All of the files for the library are copied to the node_modules folder including react. So when npm link is used the consuming application will detect 2 different reacts and crash. The current suggested workaround is to delete react and react-dom from the library build before installing into the consuming application.
Set up an NPM toolchain that can take react, redux, material-ui, and router then output NPM library files. These files should be ready to be deployed as an NPM package by running a script command such as
npm run build-library
The components should be tested to work on other react libraries. This can be done using
npm link <library name>
The text was updated successfully, but these errors were encountered: