René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Cannot extend lint process anymore","articleBody":"With the release of the `beta28` version and due to [this PR](https://github.com/angular/angular-cli/pull/4248/files), we cannot extend the `ng lint` command which is a serious regression for my projects.\r\n\r\nWith the previous `beta26`, by changing the `npm scripts` section we could extend the lint process like this:\r\n```\r\n  \"scripts\": {\r\n    \"lint\": \"tslint \\\"src/**/*.ts\\\" \\\"e2e/**/*.ts\\\" \u0026\u0026 stylelint \\\"src/**/*.scss\\\" --syntax scss \u0026\u0026 htmlhint \\\"src\\\"\"\r\n```\r\n\r\nNow that this was removed, we cannot extend the behavior of `ng lint` anymore with the addition of `stylelint` and `htmllint`...\r\n\r\nThis is quite a regression, while I understand the move to the tslint API for better integration, it also complicates the process by hiding it behind JSON settings and kills any customization like the one I was doing. For the meanwhile I'll move my process to use `npm scripts` directly, but it would be nice to find some middle ground on this.\r\n\r\nThis sort of breaking changes kinda make me worry about the future of `angular-cli`, removing customization features like this are bad in a maintenance update (yeah I understand it's still beta, still).\r\n","author":{"url":"https://github.com/sinedied","@type":"Person","name":"sinedied"},"datePublished":"2017-02-02T08:26:12.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/4344/angular-cli/issues/4344"}