NODE_PATH=./node_modules grunt assets

[Danjavia]

error on windows when I excecute npm run-script assets

[mesin]

@Danjavia please provide some console output here Thanks

[Danjavia]

The console output is:

$ npm start

application@0.0.1 start c:\Users\danjavia\Desktop\Danjavia\apps\application NODE_PATH=./node_modules NODE_ENV=development DEBUG=twee.io node ./application.js

"NODE_PATH" no se reconoce como un comando interno o externo, programa o archivo por lotes ejecutable.

npm ERR! application@0.0.1 start: NODE_PATH=./node_modules NODE_ENV=development DEBUG=twee.io node ./application.js npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the application@0.0.1 start script. npm ERR! This is most likely a problem with the application package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! NODE_PATH=./node_modules NODE_ENV=development DEBUG=twee.io node ./application.js npm ERR! You can get their info via: npm ERR! npm owner ls application npm ERR! There is likely additional logging output above. npm ERR! System Windows_NT 6.1.7601 npm ERR! command "c:\Program Files\nodejs\node.exe" "c:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "start" npm ERR! cwd c:\Users\danjavia\Desktop\Danjavia\apps\application npm ERR! node -v v0.10.26 npm ERR! npm -v 1.4.3 npm ERR! code ELIFECYCLE npm ERR! npm ERR! Additional logging details can be found in: npm ERR! c:\Users\danjavia\Desktop\Danjavia\apps\application\npm-debug.log npm ERR! not ok code 0 danjavia@DIEGOSHK /C/Users/danjavia/Desktop/Danjavia/apps/application

[Danjavia]

Cannot be posible to solve this issue :(

[gelogenic]

I encountered the same error on Windows and was able to fix this by editing the package.json by removing the string ''NODE_PATH=./node_modules '' from the scripts.assets and scripts.watch values. (Windows is choking on what appear to be inline attempts to set env variable values):

    "scripts": {
        "pstart": "NODE_PATH=./node_modules NODE_ENV=production PORT=80 node ./application.js",
        "ssl-start": "NODE_PATH=./node_modules NODE_ENV=production PORT=80 sudo node ./application.js",
        "start": "NODE_PATH=./node_modules NODE_ENV=development DEBUG=twee.io node ./application.js",
        "assets": "NODE_PATH=./node_modules grunt assets",
        "watch": "NODE_PATH=./node_modules grunt watch"
    },

After (only the changed lines to save space):

"assets": "grunt assets",
"watch": "grunt watch"

I don't have time at the moment to finish troubleshooting the remaining scripts properties but posting this in case someone else has time. Here's the output from attempts at the start script with and without the offending string from above:

c:\scripts\node\tweetest\application>npm run-script start

> application@0.0.1 start c:\scripts\node\tweetest\application
> NODE_PATH=./node_modules NODE_ENV=development DEBUG=twee.io node ./application.js

'NODE_PATH' is not recognized as an internal or external command,
operable program or batch file.

npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Apps\\iojs\\\\node.exe" "C:\\Apps\\iojs\\node_modules\\npm\\bin\\npm-cli.js" "run
-script" "start"
npm ERR! node v1.2.0
npm ERR! npm  v2.6.0
npm ERR! code ELIFECYCLE
npm ERR! application@0.0.1 start: `NODE_PATH=./node_modules NODE_ENV=development DEBUG=twee.io node
./application.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the application@0.0.1 start script 'NODE_PATH=./node_modules NODE_ENV=development
 DEBUG=twee.io node ./application.js'.
npm ERR! This is most likely a problem with the application package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     NODE_PATH=./node_modules NODE_ENV=development DEBUG=twee.io node ./application.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls application
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     c:\scripts\node\tweetest\application\npm-debug.log

c:\scripts\node\tweetest\application>npm run-script start

> application@0.0.1 start c:\scripts\node\tweetest\application
> NODE_ENV=development DEBUG=twee.io node ./application.js

'NODE_ENV' is not recognized as an internal or external command,
operable program or batch file.

npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Apps\\iojs\\\\node.exe" "C:\\Apps\\iojs\\node_modules\\npm\\bin\\npm-cli.js" "run
-script" "start"
npm ERR! node v1.2.0
npm ERR! npm  v2.6.0
npm ERR! code ELIFECYCLE
npm ERR! application@0.0.1 start: `NODE_ENV=development DEBUG=twee.io node ./application.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the application@0.0.1 start script 'NODE_ENV=development DEBUG=twee.io node ./app
lication.js'.
npm ERR! This is most likely a problem with the application package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     NODE_ENV=development DEBUG=twee.io node ./application.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls application
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     c:\scripts\node\tweetest\application\npm-debug.log

c:\scripts\node\tweetest\application>

[Danjavia]

Thanks @gelogenic I will to try this. :)

[mesin]

http://pastebin.com/VBkD3Jig It seems here's correct solution. Try it. The fix of this problem will be released with version 1.0 in few weeks Thanks guys for your patience

[Danjavia]

Thanks The project is cool, I want to use in new project now.

[jcrunge]

if you are working in different operating systems you could add "cross-env" like this:

"start": "cross-env NODE_PATH=./node_modules ...",

[mesin]

Guys this framework is not supported anymore. Currently I'm using Next.js universal holistic application built with lots of features and well organized. I would like to build next generation of nextjs framework, with all these features connected in more beautiful and pluggable way.