aurelia / new

The Aurelia 2 scaffolding repo used by our tools to setup new projects.
MIT License
37 stars 18 forks source link

DevAliases cause waring/error to be shown in console #99

Open ivanbacher opened 7 months ago

ivanbacher commented 7 months ago

When creating a new project using npx makes aurelia a webpack.config file is created.

It has this line in it:

alias: production ? {
  // add your production aliases here
} : {
  ...getAureliaDevAliases()
  // add your development aliases here
}

However, since beta 12. I get this warning/error in the console:

main.js:6 [DEV:aurelia] Error: AUR0153: Element {{0}} has already been registered.

I am only importing router-lite.

This solves the issue and does not seem to break anything.

alias: production ? {
  // add your production aliases here
} : {
  // ...getAureliaDevAliases()
  // add your development aliases here
}

is this getAureliaDevAliases() needed? What does it do?

bigopon commented 7 months ago

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.

bigopon commented 7 months ago

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

ivanbacher commented 7 months ago

Super. Thanks for the info.

So that means I can just ignore the Element has already been registered warning during development?

3cp commented 2 months ago

@bigopon is this fixed?

bigopon commented 1 month ago

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.