CoffeeScript 2 support

[michaelforrest]

I'd like to try CoffeeScript 2 in my project but I get [email protected] requires a peer of [email protected] but none was installed.

I'll see what happens if I change this and submit a PR if it seems to work okay?

[michaelforrest]

Or I could try this for now iHaiduk@9e759db

[alexander-akait]

@michaelforrest seems CoffeeScripts v2 in beta, i think it is breaking changes. Let's wait stable release and upgrade loader deps

[buhrmi]

So it looks like the peerDependencies in package.json have been updated to work with coffeescript 2, but the the package version was kept at 0.7.3. Could you update the version (probably 0.8.0) and publish it on npm?

[beeplin]

agree. The previous commit (5c5e35a) has done the coffeescript2 support, but not published to npm yet.

[molszanski]

Npm publish pls? :) Even with a beta tag

[buhrmi]

what's the holdup? we're all waiting :o

[objectkit]

Hoping to use coffeescript-beta3 in pending web pack project. Could you let us know the NPM publish ETA please?

WORKAROUND
Running cd node_modules && ln -s coffeescript coffee-script from project root seems to be a viable short term workaround for 0.7.3...

[molszanski]

Or add this to package.json
"coffee-loader": "github:webpack-contrib/coffee-loader#0ea4d6a7cc9ffc7c8f7a0c6eb3fd3fedea9943b8",

[oedotme]

By requiring coffeescript instead of coffee-script in line 5 in 'node_modules/coffee-loader/index.js' did work for me and i was able to use jsx as v2 supports.
i don't know if an 'or' could do for both coffee-script, coffeescript

[edmiester777]

The workaround that I use is to define a module alias. The package module-alias helps you do this.
npm i --save module-alias

Then I have my package.json like this:

    "_moduleAliases": {
        "coffee-script": "node_modules/coffeescript/lib/coffeescript"
    }

And I just call require('module-alias/register') at the beginning of my application and it reroutes the "coffee-script" require to the new "coffeescript" require for CS2.

[alexander-akait]

If someone is interested in helping with coffee-loader PR welcome.

[renchap]

@evilebottnawi 5c5e35a switched from coffee-script to coffeescript (the new package name). This allows using coffee-loader with CoffeeScript 1 and CoffeeScript 2 (with coffeescript@beta).

The problem is that coffee-loader has not been released on NPM, so people need to rely on the git version or some hacks. If you can get a new coffee-loader released on NPM, this would solve the issue :)

[alexander-akait]

@renchap Send request on release in slack, thanks!

[beeplin]

thanks @evilebottnawi . That would be a life saver! 👍

[joshwiens]

@renchap - Latest master has been released as 0.8.0. Changelog with the permanent information for this release can be found here

[renchap]

@d3viant0ne Thanks a lot!
I can confirm CoffeeScript 2 integration works with Webpack (2.6). My package.json contains:

{
  "dependencies": {
    "coffeescript": "next",
    "coffee-loader": "^0.8.0"
  }
}

This issue should be closed.

[c5n8]

Does anybody use coffescript 2 in nuxt vue component? I am trying to get it works, but still failing.
[email protected] is used.

 ERROR  Failed to compile with 1 errors                                                                                      13:10:20

 error  in ./pages/index.vue


/home/chabib/Code/mediaplan/pages/index.vue
  15:13  error  Parsing error: Unexpected token, expected ;

  2 | 
  3 | export default
> 4 |   components:
    |             ^
  5 |     {
  6 |       Logo
  7 |     }

✖ 1 problem (1 error, 0 warnings)


 @ ./.nuxt/router.js 7:9-75
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi webpack-hot-middleware/client?name=client&reload=true&timeout=3000&path=/__webpack_hmr ./.nuxt/client.js

Here's the code:

index.vue

...

<script lang="coffee">
import Logo from '~/components/Logo.vue'

export default
  components:
    {
      Logo
    }

  data: ->
    id: 1
</script>

...

package.json

...

  "devDependencies": {
    "babel-eslint": "^7.2.3",
    "coffee-loader": "^0.8.0",
    "coffeescript": "^2.0.1",
    "eslint": "^4.3.0",
    "eslint-config-standard": "^10.2.1",
    "eslint-loader": "^1.9.0",
    "eslint-plugin-html": "^3.1.1",
    "eslint-plugin-import": "^2.7.0",
    "eslint-plugin-node": "^5.1.1",
    "eslint-plugin-promise": "^3.5.0",
    "eslint-plugin-standard": "^3.0.1",
    "pug": "^2.0.0-rc.4",
    "pug-loader": "^2.3.0",
    "stylus": "^0.54.5",
    "stylus-loader": "^3.0.1"
  }

...

[c5n8]

Welp, looks like when using coffescript I have to disable eslint

[garviand]

Still get the same error

in package.json

"coffee-loader": "0.9.x",
"coffeescript": "2.1.x",

error:

Error: ./views/js/main.coffee
Module parse failed: Unexpected token (17:11)
You may need an appropriate loader to handle this file type.

Note that the file in question contains jsx, which should be natively supported

[molszanski]

@garviand, what do you mean by "the same"?

Just to be sure, have you tried completely removing node_modules and reinstalling it again? Just to make sure you are really using the latest versions?

[garviand]

An error on my end. I was compiling coffeescript before calling webpack functions... Sorry!