-
-
Notifications
You must be signed in to change notification settings - Fork 134
Issues: aurelia/cli
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
webpack.netcore.config.js should pass environment/arguments to webpack.config
#1163
opened Feb 21, 2020 by
alexisszabo
Aurelia CLI run webpack task assumes
config.entry.app
exists
#1144
opened Aug 19, 2019 by
JSeligsohn
aurelia-cli 1.0.0 - .NET Core project with Aurelia built-in bundler does not start
#1108
opened Jun 3, 2019 by
nenadvicentic
Npm package 'qrcode' causes Uncaught RangeError: Maximum call stack size exceeded
#1086
opened Apr 8, 2019 by
CollinHerber
ESNext webpack via au build not using aurelia_project.environments file values
#1077
opened Mar 25, 2019 by
ajoslin103
[RFC] Better way of handling environment files (config files)
#1039
opened Feb 6, 2019 by
avrahamcool
ASP.NET Core with Aurelia-CLI and RequireJS does not create .NET Core project
#1020
opened Jan 18, 2019 by
nenadvicentic
Karma Unit Test Failures: Cannot find 'babel-plugin-instanbul'
#1016
opened Jan 14, 2019 by
LilSebastian5000
Babel loose config option causes issues with spread transform
#1000
opened Dec 10, 2018 by
AshleyGrant
Undesirable behaviour of webpack dev server using CLI generated config
#985
opened Nov 23, 2018 by
chrisckc
webpack resolves symlinked child node_modules due to unused nodeModulesDir in template
#961
opened Nov 2, 2018 by
jbockle
[BUG] with webpack, inlineView deps (<require from="./style.css"></require>) doesn't work
#911
opened Aug 15, 2018 by
3cp
Webpack/Karma tests fail when related elements use slots
bug
#824
opened Feb 12, 2018 by
jholland918
Previous Next
ProTip!
Follow long discussions with comments:>50.