@jeremyholt I could not reproduce it. Did you do something between “all working now” and “problem is back again”?
Sorry @jeremyholt I was testing with different code after https://github.com/aurelia/cli/pull/951
Please use "aurelia-cli": "huochunpeng/cli#tt1". Thx!
@jeremyholt aurelia-cli 1.0.0-beta.3 is released. Let us know whether it works for you. Thx!
1 Like
Good morning @huochunpeng .
1.0.0-beta.3 I just did au run --watch and everything seems to be fine. I’ll report back if I see any more problems.
Many thanks for all of your help
For the record - just amazing feedback loop with you. That’s the reason I’ve stuck with aurelia since the start. Mind you I sometimes feel that I need a degree in black magic …
1 Like
Mind watch option is removed. Watch mode is on for “run” by default, no way to turn it off.
With the webpack plugin, if there are any errors in the code (ts) it refuses to compile.
Is there any way of setting a flag to force au to fail the build if there are any errors/tslint warnings? When the screen scrolls in terminal I don’t always see that there are compilation errors (failed tslint). Sometimes I want to be able to compile irrespective of the tslint warnings, othertimes I would like the build to fail.
Note that in webpack if there are any errors/warnings the build always fails. Initially, it was a pain, but it forced me to make sure e.g. that I wasn’t using “any unused variables” etc.
You can add this to package.json scripts section.
"build": "tsc --noEmit && au build --env prod"
npm run build will do type check with tsc before running build.
The behaviour of ignoring error is not from cli itself.
It’s this line in transpile.ts:
.pipe(plumber({ errorHandler: notify.onError('Error: <%= error.message %>') }))
gulp-plumber "Prevent pipe breaking caused by errors from gulp plugins"
You could conditionally skip that line if environment is “prod”.