Missing Tasks

[jdanyow]

• prepare release task (bump version, changelog). 🔥
• lint task (need to add tslint) 🔥
• doc task: api.json generation is broken. typedoc does not yet support typescript 2.0 🔥
• doc task missing the ability to build examples
• dev tasks are missing

[niieani]

As for the Release Task, I'd go back to proposing semantic-release instead. If we can agree on a time and date I can do a screencast to show the interested parties (CC: @EisenbergEffect) how it works and why it's a simpler/better/faster workflow than doing manual releasing; handling version bumping and changelog automatically.

[plwalters]

Is there a preference for how these should be implemented? If not then we can port over the associated gulp tasks to handle those scenarios. If the idea is to keep them as npm scripts then perhaps more discussion is needed.

[AdamWillden]

As everything in aurelia is already using eslint, that would be my preference to use. I was just wondering if you were aware of this:

https://github.com/eslint/typescript-eslint-parser
https://github.com/nzakas/eslint-plugin-typescript

They have made tremendous progress over the last month from what I can see, although it is unfortunately still early days. There was something about tslint I wasn't such a fan of but couldn't quite put my finger on!

---

Obviously whatever choice you make is fine. Just wanted to make you aware of the eslint efforts for typescript in case you weren't.

[niieani]

TypeDoc is 2.0 ready now.

[niieani]

@AdamWillden I'm aware of the TypeScript eslint plugin, it's awesome. I'd be happy to switch as soon as they mature a bit more if the rest of the team is okay with it.

[jdanyow]

I've been using tslint for TypeScript projects. Is there a compelling reason why eslint would be used instead of tslint?

[AdamWillden]

There's no good reason, it's probably just due to familiarity with eslint. Is there a tslint config in the works for aurelia, like the eslint one exists in aurelia-tools?

I also thought you could use the existing eslint config and extend it for typescript rather than maintaining two different linting configurations.

[niieani]

Yeah, that's the main reason - you get less maintenance, since you can keep the JS eslint config just adding the TS-specific options. I think eslint has a better extensibility story too. But yeah, it's not production-grade yet, so we should keep tslint for the time being.

[MeirionHughes]

If this is to be the de facto standard for the rest of the repos, have you considered adding support for debugging (the specs) in vscode? I do this myself in https://github.com/aurelia/pal-nodejs . Personally, I find it extremely productive to be able to click on any source file to add a breakpoint and press f5 to build and test the library.

[jdanyow]

@MeirionHughes - the tests are written in TypeScript.

re: breakpoints - in my experience with this package and other packages, I'm typically debugging in the context of a broken test case, using the chrome instance launched by karma. I'm definitely willing to try a new approach. Do you want to tackle this in another issue/PR- I'm interested in seeing what you're doing.