mirror of
https://github.com/DavidAnson/markdownlint.git
synced 2026-04-25 01:05:55 +03:00
[GH-ISSUE #84] Consider using TypeScript or similar for newer ES features #69
Labels
No labels
bug
enhancement
enhancement
enhancement
fixed in next
fixed in next
fixed in next
new rule
new rule
new rule
pull-request
question
refactoring
refactoring
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/markdownlint#69
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @JoshuaKGoldberg on GitHub (Oct 30, 2017).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/84
+1 to using TypeScript in particular, but anything like it or Babel would be nice.
@DavidAnson commented on GitHub (Oct 30, 2017):
I prefer to avoid compilation for the core scripts. I’ve used Babel in the past and found it to be big and slow. Keeping the code on ES5 makes supporting older Node versions easy. If/when that change, I’d look at moving to ES6 directly (no compiler).
@JoshuaKGoldberg commented on GitHub (Oct 30, 2017):
Have you tried TypeScript with ES3/ES5 output?
tsc -wis pretty speedy. :)@DavidAnson commented on GitHub (Oct 30, 2017):
We use TS->ES5 at my day job. :) It sounds better than Babel, but still adds complexity/dependencies.
@DavidAnson commented on GitHub (Apr 27, 2018):
Commit
18125a1872updates supported Node versions to 6+, supporting most new ES features (http://node.green/).Commit
78c1af7bfdadds TypeScript to the demo script to maintain ES3 support for older browsers.