-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Generate node with coffeescript #92
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
Comments
Hi, thats right, at the moment only the the client side generates with coffeescript. But if you'd like to make a PR that adds support for server side CS go for it :) |
I'll work on that, I just don't know yet how make yo generate with the coffee files instead js. To watch, compile and serve I already know. Do you have any idea? |
|
You didnt understand, I was talking about that at the time I don't know how I'll make it generate the server side when you use --coffee parameter, I have to take a look. But I know how to edit the gruntfile to watch, compile and serve if the .coffee files are already there, that is what I mean. I'll take a look how I can generate, If do you know where I can start looking that will be great |
Oh sorry, I see what you mean. It probably should do something like the copyScriptWithEnvOptions function does for selecting the js or coffeescript client side files. |
Any hints on setting up the gruntfile for doing this? Perhaps a working example gruntfile.js? I've already generated my site, so I'm not looking for --coffee support in the generator, just an example of what it would have done so I can set up the watches, etc without breaking the existing gruntfile :) |
I tried to create my app with coffeescript but just the angular was generated with CS.
If I create a new .coffee file in the node's controller the file is not compiled with grunt coffee.
Did I missed something or this feature does not work?
If not I'll try to change it and make a pull request. :)
The text was updated successfully, but these errors were encountered: