-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to hawtio 1.0.4 + causes compile / runtime errors #340
Comments
@tadayosi Initially, thought it must be the dependency upgrades I merged in, yesterday, but taking out a branch and going back to prior to the upgrades, these errors pop up the moment that I upgrade I have some kind of fix / workaround for the
The second error is more of a problem and frankly I am stumped. It appears that the upgrade of
Have tried a couple of things like defining the mf/utilities version in hawtio-online and trying to ignore the library in the webpack config but nothing has worked. So am just not sure how to proceed with this so please any suggestions would appreciated. |
Yeah they are all known issues. For
Note only Next, for the MF utilities, it's actually just a warning, so you can ignore it when running locally.
However, with |
Note the latest |
1.0.7 released: https://github.com/hawtio/hawtio-next/releases/tag/v1.0.7 |
* Pin victory-core resolution to 36.8.6 to remove warning about react/charts * management-service.ts * Fix casting compilation error * Suppress Critical Dependency expression warning
* Pin victory-core resolution to 36.8.6 to remove warning about react/charts * management-service.ts * Fix casting compilation error * Suppress Critical Dependency expression warning
PR for 1.0.7 -> #347 |
* Pin victory-core resolution to 36.8.6 to remove warning about react/charts * management-service.ts * Fix casting compilation error * Suppress Critical Dependency expression warning
After upgrade to 1.0.4 (or 1.0.5 or 1.0.6), these errors are presented when starting the dev-server.
The text was updated successfully, but these errors were encountered: