Skip to content
This repository has been archived by the owner on Jul 7, 2019. It is now read-only.

Cloned and can't get repo to start #2

Open
Darthmaul opened this issue Jun 13, 2017 · 3 comments
Open

Cloned and can't get repo to start #2

Darthmaul opened this issue Jun 13, 2017 · 3 comments

Comments

@Darthmaul
Copy link

Hello @diegoddox !

This repo is exactly what I need for a project I'm working on. I'm trying to at least reproduce the demo to get this started, and I can't get it to start. Here's my error

 $npm start

> [email protected] start C:\Users\Karen 2.0\Documents\GitHub\react-notification-center
> better-npm-run dev-server

running better-npm-run in C:\Users\Karen 2.0\Documents\GitHub\react-notification-center
Executing script: dev-server

to be executed: "./node_modules/.bin/webpack-dev-server --hot --inline --config build/webpack.config.js"
'.' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `better-npm-run dev-server`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Karen 2.0\AppData\Roaming\npm-cache\_logs\2017-06-13T05_07_18_601Z-debug.log

Looks like stuff here hasn't been updated in about a year, so if this is no longer updated I understand. I just need a point in the right direction and I can hopefully update this stuff to the latest practices.

Thanks so much!

Andrew

@diegoddox
Copy link
Owner

diegoddox commented Jun 24, 2017

@Darthmaul this may be because you're running on Windows machine, try this on the project folder.

NODE_ENV=development NODE_PORT=4001 ./node_modules/.bin/webpack-dev-server --hot --inline --config build/webpack.config.js

@Darthmaul
Copy link
Author

I'm not what you mean by this? I tried to run this through the terminal and it said it was unrecognized. As far as pasting it somewhere I'm not sure where I would. Sorry!

@sibamohanty995
Copy link

sibamohanty995 commented Jun 29, 2017

just put the absolute path instead of ./node_modules, as it is not able to recognize the path of the folder. so just go to the node modules folder and copy paste the location of the folder in your package.json and you will be able to run it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants