You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if you are looking for help from the gulp team or community, open a discussion.
if you think there is a problem with the plugin you're using, open a discussion.
if you think there is a bug in our code, open this issue.
Our thoughts on feature requests
Lots of developers rely on gulp, so we don't make big changes very often. Not every feature request will be added to gulp, but hearing about what you want is important. Don't be afraid to submit a feature request!
Thanks for the request. We'll be looking to the community to help implement this; otherwise it won't land in gulp 5 because we have a ton other work to do.
Before you open this issue, please complete the following tasks:
use the search bar at the top of the page to search this repository for similar issues or discussions that have already been opened.
if you are looking for help from the gulp team or community, open a discussion.if you think there is a problem with the plugin you're using, open a discussion.if you think there is a bug in our code, open this issue.Our thoughts on feature requests
Lots of developers rely on gulp, so we don't make big changes very often. Not every feature request will be added to gulp, but hearing about what you want is important. Don't be afraid to submit a feature request!
Describe your idea for a new feature
Add support for loading
.mts
files, same as.cts
.Explain the problem your idea is trying to solve
I'd like to use native ESM modules, while also using TypeScript. This is what the
.mts
extension was made to accompplish.How will it benefit gulp and its users?
Allow loading native ESM modules in node while also using TypeScript to do type-checking.
If this feature could exist outside of gulp (like as a plugin or a module), would you be interested in helping to create and maintain it?
It already exists in
ts-node
The text was updated successfully, but these errors were encountered: