Skip to content
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

Use of @beemo/core 0.27 is broken because of upstream changes #17

Open
camflan opened this issue Feb 12, 2020 · 0 comments
Open

Use of @beemo/core 0.27 is broken because of upstream changes #17

camflan opened this issue Feb 12, 2020 · 0 comments

Comments

@camflan
Copy link

camflan commented Feb 12, 2020

This has broken @data-ui builds (and maybe/probably others)

This repo is using @beemo/core 0.27.0 which depends on @boost/core ^1.9.0. @boost/core now resolves to 1.18.2.
The problem is that @boost/core 1.18.2 relies on optimal ^4.2.0 which has a lot of breaking changes including the change from Builder to Predicate

The affect this has is that Optimal throws Unknown blueprint for "configure". Must be a predicate. during building because the config is still ShapeBuilder instead of ShapePredicate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant