search

strongloop / strong-pm

deployer for node applications
http://strong-pm.io
Other
1k stars 71 forks source link

CoffeeScript support #225

Closed fuson closed 9 years ago

rmg commented 9 years ago

@fuson can you elaborate?

fuson commented 9 years ago

For now in our web project we use PM2 with keymetrics monitoring dashboard, but looking to strong stack and "interpreters" support (in design not only coffee) looks like a primary showstopper to initiate migration activities. And i'm NOT sure that this project is the proper place to implement it, you have "strong-runner", "loopback", "strong-supervisor" and another projects that looks like a candidate :) Anytime, we like your CRUD solution :)

rmg commented 9 years ago

Understood. You essentially want to override process.execPath so that your app is run by /usr/local/bin/coffee (or ./node_modules/.bin/coffee) instead of/usr/local/bin/node`.

Is pre-compiling your app in a prepublish script not a workable solution for you?

fuson commented 9 years ago

But what we receive in stack traces? .js line numbers that is absolutely irrelevant with .coffee code? Its not a good idea :(

And execPath as i understand is not a solution for clustering, require('coffee-script/register') needed. You may try look at implementation in pm2 by searching "coffee" on their repo.

rmg commented 9 years ago

My execPath comment was more about intent than actual implementation.

As for stack traces, I had assumed the coffee compiler took care of that, otherwise it wouldn't be so popular. Seems I was mistaken.

sam-github commented 9 years ago

We support coffee if you use slc build, and a prepublish or build script