-
Notifications
You must be signed in to change notification settings - Fork 9
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Ncapsulate.Grunt has an incorrect path for node command #2
Comments
It should be referencing back to the version of node in the packages I'll take a look, as it why it might be breaking. Between updating, I have On Mon, May 12, 2014 at 12:04 PM, munkyjunky notifications@github.comwrote:
|
I've also been having issues where no commands in grunt.targets are being |
Sorry I've been unable to get to this until now, been fairly busy. I've been contemplating removing the .cmd files from the content area of the nupkg. It seems the concurrent access is causing issues when installing, updating and uninstalling. I've run into this myself now as well. The one concern I have is that then the .cmd files will have to be manually added to source control, which for something like Git isn't all that bad with the VS Tools for Git, but something like TFS it could be easy to forget to add them. I suppose I could add a readme.txt that pops up and informs the user about what they need to do. Does that sound viable? |
…n disk when installing the first time. Add a readme.txt file to make sure that users understand they must be part of source control.
I've put the change in discussed above, let me know if solves your issue. In local testing, it appears to solve the problem, but I'll keep this open for a little while to make sure it does indeed solve it. |
That seems to have fixed that issue. I can run the grunt command and it's working as expected (from the command line). It's a bit annoying to have to manually include those files in source control, but functionally it seems to work, bar the below.
|
After installing Ncapsulate.Grunt from Nuget, which installed Ncapsulate.Grunt 0.4.4.3 & Ncapsulate.Node 0.10.26, the grunt.cmd file references /nodejs/node, which does not exist.
I fixed this locally by altering grunt.cmd to:
The text was updated successfully, but these errors were encountered: