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

Running babel on .coffee or js.coffee files #59

Open
thijsc opened this issue Jan 31, 2017 · 2 comments
Open

Running babel on .coffee or js.coffee files #59

thijsc opened this issue Jan 31, 2017 · 2 comments
Labels

Comments

@thijsc
Copy link

thijsc commented Jan 31, 2017

Thanks for this amazing gem! Really helping us out. We ran into an issue, not sure if this is a bug of something we're misunderstanding:

We're running the React preset over all files like so:

{
  "presets": [
    "react",
    "es2015"
  ]
}

This works well for .js files written in ES2015, JSX segments get converted. For Coffeescript files (with both .js.coffee and .coffee extensions) the babel step isn't run. Is there a way to have Bable run after the Coffeescript files have been converted to normal Javascript by the asset pipeline?

@thijsc thijsc mentioned this issue Jan 31, 2017
@bouk
Copy link
Contributor

bouk commented Feb 1, 2017

I'm afraid this is not going to be supported, as it would break the workflow we're using at Shopify. I think you'll have to fork and fix the gem to make this work

@bouk bouk added the wontfix label Feb 1, 2017
@thijsc
Copy link
Author

thijsc commented Feb 1, 2017

I'll look into forking or alternative solutions to our problem then. Curious: What would break in your workflow?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants