[CS2] coffeescript-loader

[michael-ciniawsky]

👋 We currently are a bit clueless how to handle upgrading coffeescript-loader to coffescript v2, the 'problem' is the package rename between v1/v2 from coffee-script to coffeescriptsince we handle the version via peerDependencies atm. But also coffeescript@latest seem to point to v1.12.x (v1), which would be fine for v1 support in coffeescript-loader. Can someone please confirm that at least versions >= 1.12 of the v1 branch will be available under coffeescript aswell? Thx in advance 😛

[mrmowgli]

Same question here. My understanding is that in npm you can link in whatever version you want for latest or stable? The work around I am using currently is to symlink node_modules/coffeescript@next to node_modules/coffee-script The coffee-script branch isn't being changed yet to avoid accidental upgrades. It's also possible to do some magic with local npm repos or possibly Yarn.

…

On Mar 12, 2017 8:17 PM, "Michael Ciniawsky" ***@***.***> wrote: 👋 We currently are a bit clueless how to handle upgrading coffeescript-loader to coffescript v2, the 'problem' is the package rename between v1/v2 from coffee-script´ tocoffescriptsince we handle the version viapeerDependenciesatm. But ***@***.*** to point tov1.12.x(v1), which would be fine for v1 support incoffeescript-loader. Can someone please confirm that at least versions >= 1.12 of the v1 branch will be available undercoffeescript`? Thy in advance 😛 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#4462>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABy6x4HjqwhlOr8MFErGp5dnM2lPjqu-ks5rlLUtgaJpZM4MazaV> .

[michael-ciniawsky]

@mrmowgli yep, the tricky thing isn't setting e.g coffee-script && coffeescript in peerDependencies but when require() them both in the loader => Error

[jashkenas]

Pinging @GeoffreyBooth for his plans on this...

[GeoffreyBooth]

The plan at the moment is that coffeescript will have all versions (going back to 1.8.x or so) through the latest, including future versions of 2.x (and 1.x if there are any more). Future releases of 2.x will be on coffeescript. You can simply consider coffeescript to be the new primary NPM module name for CoffeeScript.

coffee-script for now will only get the latest 1.x releases. If we determine that it’s safe for downstream tools to put 2.x on it as well, then it will become a mirror of coffeescript. But for now it’s stuck at 1.x, so please change your code to use coffeescript instead.

[michael-ciniawsky]

@GeoffreyBooth Awesome 👍 just to confirm coffeesscript set as peerDependency will definitely not 'exclude' v1 users using >= 1.8.x ? 🙃 Can we use it now or is it in the transition phase?

[GeoffreyBooth]

@michael-ciniawsky You can use it now. coffeescript should already have all the same old versions as coffee-script, except I think it was 1.7.0 which NPM wouldn’t let me publish (I guess because it had already been published and unpublished). If that’s an issue I can reach out to NPM and ask them to override.

Also when I published I went by git tags; if someone happened to npm publish a version from a commit different than what was tagged, then the two repos have slightly different versions with the same version number (grr). But I don’t think that happened for any versions, at least not for any 1.12.x versions. Again if it did I hope the NPM maintainers would fix it for us.

[michael-ciniawsky]

@GeoffreyBooth kk we'll see 😛 should normally be fine. Last question 🙃, are there any breaking changes in the Node API between v1 => v2 ?

[GeoffreyBooth]

Aside from requiring coffeescript or coffeescript/register instead of coffee-script, no. See http://coffeescript.org/v2/#breaking-changes

[GeoffreyBooth]

But CS2 requires Node 7+; the compiler itself is now in ES2015 (features supported by Node 7 only) so that’s one thing to be aware of.

[michael-ciniawsky]

@GeoffreyBooth Alright thx appreciated

[miloslavnosek]

What do I do to use CS2 with coffee-loader? It keeps telling me that I need [email protected] to fullfill it's peer dependency and won't let me compile anything. I have coffeescript 2.0.0-beta2 in my project.

[GeoffreyBooth]

That's a question for coffee-loader. See webpack-contrib/coffee-loader#39