it seems like the default is to convert to es6 exports, and the only flag available to me also switches it to es6 exports
so essentially there's no option to explicitly say "use commonjs"
strangely enough, it respected it with some files but not others
I just manually changed the imports back to require statements
@bitmage Oops, sorry, I had this closed and I guess I hadn't set up email notifications. Strange that it would convert to ES6 import/exports. If you still have an example file where that happens, you could paste into the repl ( http://decaffeinate-project.org/repl/ ) and see if it happens there.
@keeganstothert CS2 isn't supported at the moment but it's possible it'll just work or only need minor modifications, depending on what features you're using. There's a project called depercolator that wraps decaffeinate and cjsx-transform that you might find useful: https://github.com/bugsnag/depercolator . See this blog post about it: https://blog.bugsnag.com/converting-a-large-react-codebase-from-coffeescript-to-es6/
Hi @WEB-WORKER, new JS code should be using
let or const for all variable declarations and never use var, so decaffeinate always prefers const or let when possible. Some explanation is in the eslint rule docs: https://eslint.org/docs/rules/no-var
i've some trouble to checkout the src to do some local development. on master (and on v.4.8.8) the linter always shows some errors s.t. npm install or npm run build always fails
totally new to js and coffee, and viola just seen decaffeinate, I wonder: coffeescript is dead?
Hey @tuyenpm9 . CoffeeScript has been losing popularity, and it's much more common for new projects to be in JavaScript now, and of course decaffeinate is designed to help people move off of CoffeeScript. That said, CoffeeScript has been revitalized a bit with CoffeeScript 2.0, so you may want to check it out, but I'd still recommend JavaScript (or TypeScript) for new projects.
What coffeescript repl you use?
@eventualbuddha, I typically just use the one at https://decaffeinate-project.org/repl/ if I need to examine something. What are you trying to do with the repl?
say, I wanna recognize some coffeescript node type
I forget what ast repl I can use for coffee
@alangpierce
just ran across decaffeinate.. looks to be meant for converting coffee to plain JS as a one time step. I want do do a PR to an existing library that's written in coffeescript to add an ES6 output (currently the dist build only contains requirejs/amd/systemjs). Is it possible to set up decaffeinate (or bulk-decaffeinate) as a build step?
Thanks for making this project! Just managed to decaffeinate a racing game :) CodeArtemis/TriggerRally#76
Hi, i have the following decaffeinated code:
/*
* decaffeinate suggestions:
* DS102: Remove unnecessary code created because of implicit returns
* DS206: Consider reworking classes to avoid initClass
* Full docs: https://github.com/decaffeinate/decaffeinate/blob/master/docs/suggestions.md
*/
angular.module("resources").factory("AdminTerritory", [
"RailsResource",
function (RailsResource) {
let AdminTerritory;
return (AdminTerritory = (function () {
AdminTerritory = class AdminTerritory extends RailsResource {
static initClass() {
this.configure({
url: Routes.admin_territories_path(),
name: "territory",
pluralName: "territories",
interceptors: ["IndexMetadataInterceptor"],
});
}
};
AdminTerritory.initClass();
return AdminTerritory;
})());
},
]);how to rework initClass ?
i did the following but it is not working:
angular.module("resources").factory("UserCalendarItem", [
"CalendarItem",
function (CalendarItem) {
let UserCalendarItem;
return (UserCalendarItem = (function () {
UserCalendarItem = class UserCalendarItem extends CalendarItem {
constructor() {
super();
this.configure({
url: Routes.user_calendar_items_path("{{userId}}"),
});
}
};
return UserCalendarItem;
})());
},
]);
any ideas?