-
Notifications
You must be signed in to change notification settings - Fork 17
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
Update aurelia-flux to support aurelia-framework 0.15 #11
Comments
This happened before with aurelia-framework 0.14.0 -it was fixed in 0.14.1. Maybe 0.15.0 has broken things again? See: #9 |
I am seeing this now after updating everything. Apparently its broke again.
to this
it doesn't call out the pipeline error anymore. |
Changing the aurelia-router dependency as @airboss001 did also removed the issue for me and it appears to be working so far. |
If in doubt, the best way to check is to look in your If you find one, check your Most plugins I've used work fine with updates without any work needing to be done to the plugin itself - but obviously if you have mixed framework libraries in a project there's no guarantee that the APIs will match up ok, especially at this early stage with all the breaking changes - so you end up with the old loader passing a load of crap to the new view compiler etc |
I've updated all my references and I'm still getting the |
rokadias, you did not update the plugins configuration section to use the 0.11.0 router dependency, its still pointing at 0.10.4 |
Until v1 this is going to be an issue because the semver changes won't let jspm update work like it should, after v1 this should be no problem. @tfrydrychewicz can you please update? We are getting some questions in the official gitter. |
Having the same issue created #12 |
When I try to using the Aurelia-flux plugin installed using the JSPM beta, I get the following error message when running the app:
Unhandled promise rejection Error: Pipeline steps can only be added to the root router.
I am guessing the issue is that this is due to the changes made for the JSPM beta in the latest version.
I found this when I was following the steps of Blog post 1.
The text was updated successfully, but these errors were encountered: