MohanNarayana on v3.11.1
Akarshit on trunk
Release v3.11.1 Signed-off-by:… Release v3.11.1 Signed-off-by:… Merge branch 'trunk' of https:/… and 2 more (compare)
jrw421 on release-next-v3.11.1
Release v3.11.1 Signed-off-by:… (compare)
imports/*folders, and CSS-in-JS code included in the Catalyst components themselves. Definitely not easy to change stuff with a setup like that.
makeStyleswith a common MUI theme, just like the
example-storefront. Of course this will be the case of that new admin UI project which is in the pipeline. But I doubt we’ll see that happen on
reaction-admin. Too much work.
(Using Yarn because there is a yarn.lock file)
yarn install v1.21.1
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "/firstname.lastname@example.org/node_modules/@material-ui/icons/.yarn-metadata.json: Unexpected token \u0000 in JSON at position 0".
info If you think this is a bug, please open a bug report with the information provided in "/usr/local/src/app/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
yarn cache cleanthe error you posted is sort of described here too https://stackoverflow.com/questions/31547789/why-am-i-getting-unexpected-token-u0000-when-using-npm-install-g-package
reaction-adminfor Catalyst components… For the
defaultThemethough, the only solution appears to locally mutate the
defaultThemethat you’re getting from Catalyst before passing it on to your
MuiThemeProvider. Anybody let me know if there’s a better way.