-
-
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
DevAliases cause waring/error to be shown in console #99
Comments
Thanks @ivanbacher , since beta 12, there will be warning when theres a duplicate registration. Thats what the line is about. Though i missed the name of the element being registered so it appears as {{0}}. There will be a dev version with this fixed. |
And for your main question: the get dev aliases is very useful during development as it gives clear description of what some errors are, in contrast to production mode where you only see the error code. A bit more info can be found at https://docs.aurelia.io/developer-guides/error-messages |
Super. Thanks for the info. So that means I can just ignore the |
@bigopon is this fixed? |
The main issues have been fixed, only hmr related one is not. Its because we register again when we hot reload a module. With the ability to deregister, this should be fixable. |
When creating a new project using
npx makes aurelia
awebpack.config
file is created.It has this line in it:
However, since beta 12. I get this warning/error in the console:
I am only importing
router-lite
.This solves the issue and does not seem to break anything.
is this
getAureliaDevAliases()
needed? What does it do?The text was updated successfully, but these errors were encountered: