Closed ghost closed 8 years ago
Hi @pkpower I will have to look on the newer versions of node. Thanks for reporting!
Is there any update on this? I'm having the same issue.
yeah.. any updates? I'm having the same issue too.
> TARGET=build webpack
'TARGET' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "build"
npm ERR! node v4.2.6
npm ERR! npm v2.14.12
npm ERR! code ELIFECYCLE
npm ERR! react-lab@1.0.0 build: `TARGET=build webpack`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the react-lab@1.0.0 build script 'TARGET=build webpack'.
npm ERR! This is most likely a problem with the react-lab package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! TARGET=build webpack
It seems like more people are having this issue. Can you try a newer version of node? I do not have a Windows PC to test against sadly.
Thanks for reporting everyone.
Just a workaround for Windows.
var TARGET = process.env.TARGET;
to
var TARGET = 'dev';
TARGET=dev
from the scripts/start
sectionnpm start
My node version is 0.10.32Is this Azure? If it is, then I dont think the Windows server that is being used recognizes TARGET
is a command. I've adjusted it so configuration is based on process.env
variables instead of doing it inline like TARGET=build