Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add option to use Babel #11

Open
danielbayley opened this issue Oct 13, 2017 · 3 comments · May be fixed by #12
Open

Add option to use Babel #11

danielbayley opened this issue Oct 13, 2017 · 3 comments · May be fixed by #12

Comments

@danielbayley
Copy link

http://coffeescript.org/#coffeescript-2

@danielbayley danielbayley linked a pull request Oct 14, 2017 that will close this issue
@n-riesco
Copy link
Owner

@danielbayley @hoishing we have two PRs open to update jp-CoffeeScript to CoffeeScript 2. The main difference is whether we want to use Babel to transpile or not.

Personally, I favour the option of making transpilation optional (as not everyone needs it and it introduces the import issue).

We could have jp-CoffeeScript do a search for .babelrc (jp-babel does that; see here) and enable transpilation only in that case.

What are your thoughts?


@danielbayley I'm sorry I have taken so long to act on this issue.

@hoishing
Copy link
Contributor

Maybe we can just update it without Babel first, such that all users can use CoffeeScript 2 right away. Then update with Babel transpilation later if the import issue is resolved.

@n-riesco
Copy link
Owner

@hoishing OK, I'll merge your PR first.

@n-riesco n-riesco changed the title Update to CoffeeScript 2 Add option to use Babel Jun 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants