Error while installing Coffee-script@1.12.8 'invalid or unexpected token'

Question

Error while installing Coffee-script@1.12.8 'invalid or unexpected token'

Closed this issue 7 years ago · 65 comments

When I try to install like below I get the error.
I am using NPM 5.6.0 on a Windows 10 Machine .

npm install -g coffee-script@1.12.8
C:\Users\myuser\AppData\Roaming\npm\cake -> C:\Users\myuser\AppData\Roaming\npm\node_modules\coffee-script\bin\cake
C:\Users\myuser\AppData\Roaming\npm\coffee -> C:\Users\myuser\AppData\Roaming\npm\node_modules\coffee-script\bin\coffee

coffee-script@1.12.8 postinstall C:\Users\myuser\AppData\Roaming\npm\node_modules\coffee-script
node --eval 'if (require("./package.json").name === "coffee-script") { var red, yellow, cyan, reset; red = yellow = cyan = reset = ""; if (!process.env.NODE_DISABLE_COLORS) { red = "\x1b[31m"; yellow = "\x1b[33m"; cyan = "\x1b[36m"; reset = "\x1b[0m"; } console.warn(red + "CoffeeScript has moved!" + reset + " Please update references to " + yellow + ""coffee-script"" + reset + " to use " + yellow + ""coffeescript"" + reset + " (no hyphen) instead."); console.warn("Also, a new major version has been released under the " + yellow + "coffeescript" + reset + " name on NPM. This new release targets modern JavaScript, with minimal breaking changes. Learn more at " + cyan + "http://coffeescript.org" + reset + "."); console.warn(""); }'

'if
^^^
SyntaxError: Invalid or unexpected token
at createScript (vm.js:56:10)
at Object.runInThisContext (vm.js:97:10)
at Object. (eval-wrapper:6:22)
at Module._compile (module.js:570:32)
at evalScript (bootstrap_node.js:354:27)
at run (bootstrap_node.js:123:11)
at run (bootstrap_node.js:390:7)
at startup (bootstrap_node.js:122:9)
at bootstrap_node.js:505:3
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! coffee-script@1.12.8 postinstall: node --eval 'if (require("./package.json").name === "coffee-script") { var red, yellow, cyan, reset; red = yellow = cyan = reset = ""; if (!process.env.NODE_DISABLE_COLORS) { red = "\x1b[31m"; yellow = "\x1b[33m"; cyan = "\x1b[36m"; reset = "\x1b[0m"; } console.warn(red + "CoffeeScript has moved!" + reset + " Please update references to " + yellow + "\"coffee-script\"" + reset + " to use " + yellow + "\"coffeescript\"" + reset + " (no hyphen) instead."); console.warn("Also, a new major version has been released under the " + yellow + "coffeescript" + reset + " name on NPM. This new release targets modern JavaScript, with minimal breaking changes. Learn more at " + cyan + "http://coffeescript.org" + reset + "."); console.warn(""); }'
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the coffee-script@1.12.8 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\myuser\AppData\Roaming\npm-cache_logs\2017-11-30T08_12_56_775Z-debug.log

Answer 1 · 2017-11-30T08:40:01.000Z

Experiencing the same thing with npm 3.10.10 on win 10

Answer 2 · 2017-11-30T08:58:30.000Z

Seeing the same with npm 5.3.0

Answer 3 · 2017-11-30T09:11:20.000Z

To be clear, if you are able to change your dep, you should use coffeescript instead of coffee-script. The issue remains for nested deps.

Answer 4 · 2017-11-30T09:18:07.000Z

Same issue is there for Windows 10 and npm 5.5.1

Answer 5 · 2017-11-30T09:21:02.000Z

Same issue here Windows 8.1 & npm 3.5.2. Karma is loading the coffeescript package.

Answer 6 · 2017-11-30T09:33:17.000Z

I don't want to hurry you, but is there any ETA? This is a critical issue for most of us :)

Answer 7 · 2017-11-30T09:34:27.000Z

Why did not you use "deprecated" field from package.json?
We are waiting for your fix, since we have dropped the production release now. We use a third-party library that uses your library.

Answer 8 · 2017-11-30T09:35:25.000Z

As a quick workaround, you can reference an older version of the library in your package.json.
"coffee-script": "1.12.7" worked in my case.

Answer 9 · 2017-11-30T09:38:28.000Z

My package.json looks funny now with typescript and coffeescript side by side 😄 But it works, thanks @garvik

Answer 10 · 2017-11-30T09:40:24.000Z

The problem is that many third-party libraries use this library.

Answer 11 · 2017-11-30T09:43:05.000Z

+1 @pmaza. I'm new to node, is there a way to enforce the use of a version for a package globally?

Answer 12 · 2017-11-30T09:45:52.000Z

@garvik 's solution worked for me, even though I have only third party dependencies on this library.

Answer 13 · 2017-11-30T09:46:38.000Z

I don't want to hurry you, but is there any ETA? This is a critical issue for most of us :)

I do not have npm access. Paging @GeoffreyBooth.

Answer 14 · 2017-11-30T09:50:08.000Z

@meowthing I've just solved it right now installing "coffee-script@1.12.7" as a dev dependency.
Thanks @garvik!!

Answer 15 · 2017-11-30T09:54:40.000Z

Adding "coffee-script": "1.12.7" as devDependency solved it. Thanks all!

Answer 16 · 2017-11-30T10:05:57.000Z

I suppose that windows machine can't recognize the string argument wrapped in single quotes.
It should be wrapped in double quotes instead.

Answer 17 · 2017-11-30T10:58:10.000Z

Would be great to unpublish the package or publish a fix. I think this is breaking many builds on Windows (it's breaking ours at least and we don't have a direct dependency on this package)

Answer 18 · 2017-11-30T11:01:44.000Z

Or simplify this https://github.com/jashkenas/coffeescript/blob/1/package.json#L31 By just doing a console.warn and avoid all fancy things

…

On Thu, 30 Nov 2017 at 11:58, Guillaume Mouron ***@***.***> wrote: Would be great to unpublish the package or publish a fix. I think this is breaking many builds on Windows (it's breaking ours at least and we don't have a direct dependency on this package) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#4805 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQv-WnXQOcA-iQ-oYCWNfDuVw7tDblPwks5s7opRgaJpZM4QwMGf> .

Answer 19 · 2017-11-30T11:03:15.000Z

Same issue is there for Windows 7 and npm 6.11.0

Answer 20 · 2017-11-30T11:11:36.000Z

I am having the same issue where coffee-script is an internal dependency of some third party module due to which actual installation of our npm module is failing.

I am using npm 5.4.2 on windows 7.

Please release the fix as soon as possible.

Answer 21 · 2017-11-30T11:12:11.000Z

The same I installed 1.12.1 but vue-cli needs the newest and I can`t install it Windows 10 npm 5 node 8.9

Answer 22 · 2017-11-30T11:13:50.000Z

There are always two ways out, go easy and go the right way. Simple - replace double quotes or replace the library (if possible). Is correct - to make fix as soon as possible

Answer 23 · 2017-11-30T11:18:47.000Z

@GeoffreyBooth can you please communicate about an ETA ? Or unpublish the package ?

Answer 24 · 2017-11-30T11:22:13.000Z

Yes this is just a mess, hard to fix in the dependency tree..

Answer 25 · 2017-11-30T11:42:51.000Z

forwardemail/email-templates#266

Answer 26 · 2017-11-30T11:42:57.000Z

This is happening when you execute this command from the windows CMD, not from the mac or linux term, if you want to reproduce get a windows CMD and paste the node eval command that you execute on npm install

node --eval 'if (require("./package.json").name === "coffee-script") { var red, yellow, cyan, reset; red = yellow = cyan = reset = ""; if (!process.env.NODE_DISABLE_COLORS) { red = "\x1b[31m"; yellow = "\x1b[33m"; cyan = "\x1b[36m"; reset = "\x1b[0m"; } console.warn(red + "CoffeeScript has moved!" + reset + " Please update references to " + yellow + "\"coffee-script\"" + reset + " to use " + yellow + "\"coffeescript\"" + reset + " (no hyphen) instead."); console.warn("Also, a new major version has been released under the " + yellow + "coffeescript" + reset + " name on NPM. This new release targets modern JavaScript, with minimal breaking changes. Learn more at " + cyan + "http://coffeescript.org" + reset + "."); console.warn(""); }'

This will print the undesired
'if
^^^

Answer 27 · 2017-11-30T11:45:47.000Z

Me too when trying to build in VSTS. It's a dependency on jasmine-node - I'm not using it directly.

Answer 28 · 2017-11-30T11:51:56.000Z

I'm experiencing this on a mac too, doesn't seem to be a windows CMD specific issue. This was for a new installation of a package we use that depends on coffee-script

Answer 29 · 2017-11-30T11:53:53.000Z

Tried @weihsth suggestion of adding coffee-script 1.12.7 to devDependencies, but no joy. 1.12.8 keeps being used.

Is there any ETA on a fix for this??

Answer 30 · 2017-11-30T11:54:35.000Z

I've added "coffee-script": "1.12.7" to devDependencies to solve this issue (hopefully temporarily).

Answer 31 · 2017-11-30T12:27:39.000Z

It is 4:30 am in LA right now. He probably committed this right before going to bed

Answer 32 · 2017-11-30T12:30:01.000Z

Mac/Windows doesn't meter. But temporary solution with 1.12.8 works for me as well.

Answer 33 · 2017-11-30T12:39:34.000Z

This guys phone is going to be throwing notifications like a crazy mo-fo when he wakes up.

It's the new LeftPad !

Answer 34 · 2017-11-30T12:53:43.000Z

LOL Hope he sleeping well with Freddy Krueger!!

Answer 35 · 2017-11-30T13:04:19.000Z

@admeister In my case, I had to add it to dependencies instead of devDependencies ¯\_(ツ)_/¯

Answer 36 · 2017-11-30T13:12:51.000Z

Solved! added this to package.json

  "devDependencies": {
    "coffee-script": "1.12.7"
  }

This should also fix it:

  "dependencies": {
    "coffee-script": "1.12.7"
  }

Answer 37 · 2017-11-30T13:15:13.000Z

@xameeramir You have on p to many, if it's a direct copy/paste from your file, that might be the problem.
Otherwise, try adding it to dependencies, it worked in my case.

Answer 38 · 2017-11-30T13:54:06.000Z

For mission critical production requirements, there is a work around - but it's not clean.

It involves using a local npm cache too which you publish a clone of v 1.12.7 'bumped' to 1.12.8 and then have your production environment utilise that as your source for packages

npm config edit
registry=http://feeds.acme.com/

Possible options for server is https://www.npmjs.com/package/sinopia

Answer 39 · 2017-11-30T14:23:45.000Z

Would really appreciate a fast fix.

To clarify the severity of this issue: since this script breaks on Windows, it essentially breaks all packages that has coffee-script as a direct or nested dependency on Windows, including vue-cli. And since this is a nested dependency for us, we'd have to fork or ditch our direct dependency (which is hardly maintained anymore) if a prompt fix isn't possible.

Answer 40 · 2017-11-30T14:23:49.000Z

@GMouron Added as direct dep

Answer 41 · 2017-11-30T14:29:43.000Z

Same issue. I'm using jasmine-node and it has coffee-script has a dependency.
Build broken on Windows 7 with Node 8.9.1.

Answer 42 · 2017-11-30T14:30:03.000Z

Would really appreciate a fast fix.

People have posted workarounds here.
The people able to publish new versions are @jashkenas , @lydell , and @GeoffreyBooth . You'll need to wait for them to show up. There's not much else to do.

Posting "same issue" doesn't really help with anything. It's not technically difficult to solve.

Answer 43 · 2017-11-30T14:31:37.000Z

@Kylir We have jasmine-node as a dependency and when I added "coffee-script" : "1.12.7" to our dependencies it picked up this version instead of the latest, which fixed it for us. Will remove it once the real issue is fixed.

Answer 44 · 2017-11-30T14:31:43.000Z

@vendethiel there is no workaround for packages that has coffee-script as an indirect dependency, because we have no direct control over the version of coffee-script being used. The severity is being underestimated.

Answer 45 · 2017-11-30T14:36:05.000Z

@yyx990803 I don't see how it is being underestimated. There just doesn't seem to be anyone awake with npm push rights. I'm open to suggestions.

Answer 46 · 2017-11-30T14:40:14.000Z

@vendethiel no previous comments had pointed out the true implication of this bug (breaking all related packages on Windows), so it's worth pointing out. It's meaningful information and not "same issue here."

Answer 47 · 2017-11-30T14:40:39.000Z

@yyx990803 correct me if I'm wrong, but any version of coffeescript you specify will get picked up, as long as it fits in version range specified by your third-party library.

Answer 48 · 2017-11-30T14:43:12.000Z

@yyx990803 Comments from weihsth, vadimDidenko, pmaza, GMouron, BhupenderAgarwal24, ivanromakh, admeister already pointed that out. I think the point was well understood. It's critical. But there's nothing I/we can do right now.

Answer 49 · 2017-11-30T14:49:28.000Z

When production environments are unable to build - it's beyond critical and the severity should not be underestimated.

Whilst the fix is simple - and there are work arrounds these aren't suitable for everyone and for them, the delay while we wait for a fix is a costly one.

Answer 50 · 2017-11-30T14:49:31.000Z

@mbodecek good point! That is indeed a valid workaround before things gets fixed here (although not optimal as having to explicitly pin a non-direct dependency). Thanks.

Answer 51 · 2017-11-30T14:56:38.000Z

@vendethiel even though a workaround is in place, it shows a significant failing in testing and deploying this commit to a package which is incredibly popular and used in lots of popular libraries. Might be worth investigating some more robust push policies/reviewing.

Answer 52 · 2017-11-30T14:59:16.000Z

For yarn package manager need add "resolutions": { "coffee-script": "1.12.7" } to package.json

Answer 53 · 2017-11-30T14:59:48.000Z

Has anyone contacted simon.lydell@gmail.com ? He is in Stockholm and should be awake

Answer 54 · 2017-11-30T15:07:45.000Z

Same problem here when I tried to install i18n

Answer 55 · 2017-11-30T16:11:25.000Z

Using old version of keystone which uses packages that are using coffee-script 1.12.8.
Fixed by adding coffee-script: 1.12.7 to my devDependencies.

Answer 56 · 2017-11-30T16:14:24.000Z

Well, now that we have your attention 😄

I changed coffee-script latest and stable back to 1.12.7 for now.

Answer 57 · 2017-11-30T16:15:00.000Z

@GeoffreyBooth thank you :-).

Answer 58 · 2017-11-30T16:29:05.000Z

@GeoffreyBooth thanks

Answer 59 · 2017-11-30T16:55:10.000Z

So I assume the emergency is over, now that latest points to 1.12.7?

While you’re here, does anyone know how we could print this error only on direct installs, i.e. when coffee-script is in the user’s package.json, as opposed to coffee-script being installed as a dependency of some other package? Or looked at in another way, within the context of the postinstall script is there a way to detect whether we’re being installed directly versus as a dependency? See #4759.

Answer 60 · 2017-11-30T17:24:13.000Z

@GeoffreyBooth I think what you are looking for is something like; (not tested)

var fs = require('fs'),
  path = require('path');

function readJsonFile(filePath) {
  try {
    var data = fs.readFileSync(filePath, 'utf-8');
    return JSON.parse(data);
  } catch (error) {
    return null;
  }
}

var pgkCoffeeData = readJsonFile('./package.json');
if (!pgkCoffeeData || !pgkCoffeeData._where || pgkCoffeeData._where.indexOf('node_modules') !== -1) {
  return;
}

var pgkData = readJsonFile(path.join(pgkCoffeeData._where, './package.json'));
if (!pgkData) {
  return;
}

var hasOldCoffeScript = (pgkData.dependencies && pgkData.dependencies['coffee-script'])
  || (pgkData.devDependencies && pgkData.devDependencies['coffee-script']);

if (hasOldCoffeScript) {
   // oops old script is 
}

Updated implementation for anyone looking into this from the future :)

Actual implementation: https://github.com/jashkenas/coffeescript/pull/4807/files

Answer 61 · 2017-11-30T17:25:44.000Z

@GeoffreyBooth Why not just use npm-deprecate ? It's simple, built-in, fits your use case and you definitely can't break thousands of random projects with that 😃

Answer 62 · 2017-11-30T17:29:37.000Z

@GeoffreyBooth just tested it, the emergency is over

Though I have no clue how we have a dependency on coffee-script: it's not in our package.json and not in the dependency tree when printing it with "npm ls"

Answer 63 · 2017-11-30T17:46:46.000Z

@SwintDC thanks 😄

@4O4 #4759 (comment)

@alan-agius4 Let’s discuss in #4807. If there’s anyone with Windows or CI environments that can help us test, please check out that PR. I’ll aim to push a fix on Friday night, so that at least there’s the weekend for any flood of new problems. Sorry for the headache everyone.

I have until tonight to npm unpublish 1.12.8 if we want, but I’m not sure there’s a point in doing so? The 1.12.8 version can’t be reused even after I unpublish, so the fix will be in 1.12.9 regardless.

Answer 64 · 2017-11-30T17:59:43.000Z

@GabrielRatener IMHO it makes perfect sense to unpublish 1.12.8. It's faulty release, don't let anyone ever install it again for your own peace of mind.

Answer 65 · 2017-11-30T18:52:04.000Z

Okay, I’ve unpublished coffee-script@1.12.8 and coffeescript@1.12.8.