You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Started server on port 3000
/Users/zigi/Temp/after.js/node_modules/@jaredpalmer/after/scripts/start.js:100
fs.copyFile(changedPath, tempSrc.replace('src', changedPath), err => {
^
TypeError: fs.copyFile is not a function
at FSWatcher.chokidar.watch.on.changedPath (/Users/zigi/Temp/after.js/node_modules/@jaredpalmer/after/scripts/start.js:100:10)
at emitOne (events.js:115:13)
at FSWatcher.emit (events.js:210:7)
at FSWatcher. (/Users/zigi/Temp/after.js/node_modules/chokidar/index.js:198:15)
at FSWatcher._emit (/Users/zigi/Temp/after.js/node_modules/chokidar/index.js:240:5)
at FSWatcher. (/Users/zigi/Temp/after.js/node_modules/chokidar/lib/fsevents-handler.js:206:14)
at addOrChange (/Users/zigi/Temp/after.js/node_modules/chokidar/lib/fsevents-handler.js:212:7)
at FSWatcher. (/Users/zigi/Temp/after.js/node_modules/chokidar/lib/fsevents-handler.js:238:16)
at filteredListener (/Users/zigi/Temp/after.js/node_modules/chokidar/lib/fsevents-handler.js:60:7)
at /Users/zigi/Temp/after.js/node_modules/chokidar/lib/fsevents-handler.js:85:11
at Array.forEach (native)
at FSEvents. (/Users/zigi/Temp/after.js/node_modules/chokidar/lib/fsevents-handler.js:84:34)
at emitThree (events.js:135:13)
at FSEvents.emit (events.js:216:7)
at Immediate._onImmediate (/Users/zigi/Temp/after.js/node_modules/fsevents/fsevents.js:47:11)
at runCallback (timers.js:781:20)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! after@1.0.0 start: after start
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the after@1.0.0 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! /Users/zigi/.npm/_logs/2018-01-22T09_44_57_431Z-debug.log`
Hi, I get this error after any code edit. I've started with basic "hello world" app:
Mac OS - 10.13.1, node version - 8.2.1
`Your application is running at http://localhost:3000
TypeError: fs.copyFile is not a function
at FSWatcher.chokidar.watch.on.changedPath (/Users/zigi/Temp/after.js/node_modules/@jaredpalmer/after/scripts/start.js:100:10)
at emitOne (events.js:115:13)
at FSWatcher.emit (events.js:210:7)
at FSWatcher. (/Users/zigi/Temp/after.js/node_modules/chokidar/index.js:198:15)
at FSWatcher._emit (/Users/zigi/Temp/after.js/node_modules/chokidar/index.js:240:5)
at FSWatcher. (/Users/zigi/Temp/after.js/node_modules/chokidar/lib/fsevents-handler.js:206:14)
at addOrChange (/Users/zigi/Temp/after.js/node_modules/chokidar/lib/fsevents-handler.js:212:7)
at FSWatcher. (/Users/zigi/Temp/after.js/node_modules/chokidar/lib/fsevents-handler.js:238:16)
at filteredListener (/Users/zigi/Temp/after.js/node_modules/chokidar/lib/fsevents-handler.js:60:7)
at /Users/zigi/Temp/after.js/node_modules/chokidar/lib/fsevents-handler.js:85:11
at Array.forEach (native)
at FSEvents. (/Users/zigi/Temp/after.js/node_modules/chokidar/lib/fsevents-handler.js:84:34)
at emitThree (events.js:135:13)
at FSEvents.emit (events.js:216:7)
at Immediate._onImmediate (/Users/zigi/Temp/after.js/node_modules/fsevents/fsevents.js:47:11)
at runCallback (timers.js:781:20)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! after@1.0.0 start:
after start
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the after@1.0.0 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! /Users/zigi/.npm/_logs/2018-01-22T09_44_57_431Z-debug.log`
package.json:
{ "name": "after", "version": "1.0.0", "description": "", "scripts": { "start": "after start", "test": "after test --env=jsdom", "build": "after build", "start:prod": "NODE_ENV=production node build/build/server.js" }, "author": "", "license": "ISC", "dependencies": { "@jaredpalmer/after": "^0.5.2", "react": "^16.2.0", "react-dom": "^16.2.0", "react-helmet": "^5.2.0", "react-router-dom": "^4.2.2" } }
The text was updated successfully, but these errors were encountered: