3.3.0 Update "fsevents is not a constructor" when running truffle serve

Question

3.3.0 Update "fsevents is not a constructor" when running truffle serve

cameronvoell opened this issue 7 years ago · comments

After updating to truffle 3.3.0, I get the following error when running 'truffle serve' during the building truffle frontend app tutorial http://truffleframework.com/tutorials/building-testing-frontend-app-truffle-3:

##Issue

/Users/cameronvoell/.npm-packages/lib/node_modules/truffle/build/cli.bundled.js:123830
return (new fsevents(path)).on('fsevent', callback).start();
^
TypeError: fsevents is not a constructor
at createFSEventsInstance (/Users/cameronvoell/.npm-packages/lib/node_modules/truffle/build/cli.bundled.js:123830:11)
at setFSEventsListener (/Users/cameronvoell/.npm-packages/lib/node_modules/truffle/build/cli.bundled.js:123884:16)
at FSWatcher.FsEventsHandler._watchWithFsEvents (/Users/cameronvoell/.npm-packages/lib/node_modules/truffle/build/cli.bundled.js:124048:16)
at FSWatcher. (/Users/cameronvoell/.npm-packages/lib/node_modules/truffle/build/cli.bundled.js:124182:25)
at LOOP (fs.js:1758:14)
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickCallback (internal/process/next_tick.js:98:9)
Camerons-MacBook-Air:test cameronvoell$ node version
module.js:471
throw err;

I reproduced the truffle serve fail on Ubuntu 16.04 and Mac OS El Capitan 10.11 with truffle version 3.3.0 while going through this demo http://truffleframework.com/tutorials/building-testing-frontend-app-truffle-3.

Expected Behavior

When I return to truffle version 3.2.2, the problem does not exist on OSX or Ubuntu

Environment

Operating System: Ubuntu 16.04 and Mac OS El Capitan 10.11
Truffle version: 3.3.0
Ethereum client: testrpc
node version:6.11.1
npm version: 3.10.10

Rich Bodo · Answer 1 · Thu Jun 29 2017 09:46:56 GMT+0800 (China Standard Time)

I see the same on osx 10.12.5 and ubuntu 16.04.2

$ truffle serve
Serving static assets in ./build on port 8080...
/usr/local/lib/node_modules/truffle/build/cli.bundled.js:123830
  return (new fsevents(path)).on('fsevent', callback).start();
          ^

TypeError: fsevents is not a constructor
    at createFSEventsInstance (/usr/local/lib/node_modules/truffle/build/cli.bundled.js:123830:11)
    at setFSEventsListener (/usr/local/lib/node_modules/truffle/build/cli.bundled.js:123884:16)
    at FSWatcher.FsEventsHandler._watchWithFsEvents (/usr/local/lib/node_modules/truffle/build/cli.bundled.js:124048:16)
    at FSWatcher.<anonymous> (/usr/local/lib/node_modules/truffle/build/cli.bundled.js:124182:25)
    at LOOP (fs.js:1615:14)
    at _combinedTickCallback (internal/process/next_tick.js:67:7)
    at process._tickCallback (internal/process/next_tick.js:98:9)

And fsevents is installed:

npm i fsevents

> fsevents@1.1.2 install /Users/rsb/src/mozilla/truftest/node_modules/fsevents
> node install

[fsevents] Success: "/Users/rsb/src/mozilla/truftest/node_modules/fsevents/lib/binding/Release/node-v51-darwin-x64/fse.node" is installed via remote
truffle-init-webpack@0.0.1 /Users/rsb/src/mozilla/truftest
└─┬ babel-cli@6.24.1
  └─┬ chokidar@1.7.0
    └── fsevents@1.1.2

node version:

$ node --version
v7.2.0

lorepieri8 · Answer 2 · Thu Jun 29 2017 18:54:11 GMT+0800 (China Standard Time)

Same here:

Operating System: Mac OS 10.9
Truffle version: 3.2.8
Ethereum client: testrpc
node version:6.11.0
npm version: 3.10.10

`Serving static assets in ./build on port 8080...
/usr/local/lib/node_modules/truffle/build/cli.bundled.js:119780
return (new fsevents(path)).on('fsevent', callback).start();
^

TypeError: fsevents is not a constructor
at createFSEventsInstance (/usr/local/lib/node_modules/truffle/build/cli.bundled.js:119780:11)
at setFSEventsListener (/usr/local/lib/node_modules/truffle/build/cli.bundled.js:119834:16)
at FSWatcher.FsEventsHandler._watchWithFsEvents (/usr/local/lib/node_modules/truffle/build/cli.bundled.js:119998:16)
at FSWatcher. (/usr/local/lib/node_modules/truffle/build/cli.bundled.js:120132:25)
at LOOP (fs.js:1773:14)
at _combinedTickCallback (internal/process/next_tick.js:73:7)
at process._tickCallback (internal/process/next_tick.js:104:9)`

Arne Zeising · Answer 3 · Fri Jun 30 2017 06:33:26 GMT+0800 (China Standard Time)

From #448: Workaround would be to run npm run dev instead of truffle serve. Works for me on macOS 10.12.6.

samuelmantou · Answer 4 · Tue Jul 04 2017 18:43:42 GMT+0800 (China Standard Time)

Same here:

Operating System: Mac OS 10.12.5
Truffle version: 3.3.1
Ethereum client: testrpc
node version:8.1.3
npm version: 5.0.3

Serving static assets in ./build on port 8080...
/usr/local/lib/node_modules/truffle/build/cli.bundled.js:123804
return (new fsevents(path)).on('fsevent', callback).start();
^

TypeError: fsevents is not a constructor
at createFSEventsInstance (/usr/local/lib/node_modules/truffle/build/cli.bundled.js:123804:11)
at setFSEventsListener (/usr/local/lib/node_modules/truffle/build/cli.bundled.js:123858:16)
at FSWatcher.FsEventsHandler._watchWithFsEvents (/usr/local/lib/node_modules/truffle/build/cli.bundled.js:124022:16)
at FSWatcher. (/usr/local/lib/node_modules/truffle/build/cli.bundled.js:124156:25)
at gotStat (fs.js:1785:21)
at FSReqWrap.oncomplete (fs.js:152:21)

Ant · Answer 5 · Wed Jul 05 2017 04:55:40 GMT+0800 (China Standard Time)

Same here. Any fix or workaround for this?

I tried npm run dev but there is a package.json missing.

samuelmantou · Answer 6 · Wed Jul 05 2017 16:26:48 GMT+0800 (China Standard Time)

@builtwithcaffeine solve it, try this: truffle init webpack

BinGoBinBin · Answer 7 · Thu Jul 06 2017 09:35:59 GMT+0800 (China Standard Time)

@samuelmantou thanks a lot.It's work.

allan2327 · Answer 8 · Fri Jul 07 2017 22:40:07 GMT+0800 (China Standard Time)

@builtwithcaffeine Thank you worked for me..

Deleted user · Answer 9 · Sat Jul 08 2017 14:54:39 GMT+0800 (China Standard Time)

Same on windows (10):

truffle build failed too, so I used truffle compile, I don't know what the difference is as I'm still learning.

$ truffle serve

Serving static assets in .\build on port 8080...
C:\Users\David\AppData\Roaming\npm\node_modules\truffle\build\cli.bundled.js:124978
return (new fsevents(path)).on('fsevent', callback).start();
^

TypeError: fsevents is not a constructor
at createFSEventsInstance (C:\Users\David\AppData\Roaming\npm\node_modules\truffle\build\cli.bundled.js:124978:11)
at setFSEventsListener (C:\Users\David\AppData\Roaming\npm\node_modules\truffle\build\cli.bundled.js:125032:16)
at FSWatcher.FsEventsHandler._watchWithFsEvents (C:\Users\David\AppData\Roaming\npm\node_modules\truffle\build\cli.bundled.js:125196:16)
at FSWatcher. (C:\Users\David\AppData\Roaming\npm\node_modules\truffle\build\cli.bundled.js:125330:25)
at LOOP (fs.js:1755:14)
at _combinedTickCallback (internal/process/next_tick.js:95:7)
at process._tickCallback (internal/process/next_tick.js:161:9)

Ant · Answer 10 · Mon Jul 10 2017 05:10:18 GMT+0800 (China Standard Time)

@samuelmantou much thanks, this worked.

Tim Coulter · Answer 11 · Tue Jul 11 2017 04:29:00 GMT+0800 (China Standard Time)

This is a duplicate of #448. Closing for housekeeping.

Jake K. Dodd · Answer 12 · Tue Nov 21 2017 18:49:59 GMT+0800 (China Standard Time)

@tcoulter maybe change the title of #448 for those of us who run into this problem? It's clearly not limited to non-mac platforms

Sandeep · Answer 13 · Tue Dec 05 2017 20:51:56 GMT+0800 (China Standard Time)

@samuelmantou for me this worked : truffle unbox webpack

ChiragMaliwal · Answer 14 · Tue Mar 20 2018 22:20:59 GMT+0800 (China Standard Time)

truffle init webpack
Error: truffle init no longer accepts a project template name as an argument.

For an empty project, use truffle init with no arguments
Or, browse the Truffle Boxes at http://truffleframework.com/boxes!

Gandalf-Pl · Answer 15 · Tue Mar 27 2018 22:24:38 GMT+0800 (China Standard Time)

truffle init webpack
Error: truffle init no longer accepts a project template name as an argument.

For an empty project, use truffle init with no arguments
Or, browse the Truffle Boxes at http://truffleframework.com/boxes!

Fabiola B. · Answer 16 · Wed Apr 11 2018 19:09:48 GMT+0800 (China Standard Time)

truffle init webpack
Error: truffle init no longer accepts a project template name as an argument.

For an empty project, use truffle init with no arguments
Or, browse the Truffle Boxes at http://truffleframework.com/boxes!

James Peters · Answer 17 · Fri May 04 2018 20:22:37 GMT+0800 (China Standard Time)

^ I'm having the same issue as @FabiolaBusch @Gandalf-Pl @cmaliwal

ChiragMaliwal · Answer 18 · Sat May 05 2018 11:50:09 GMT+0800 (China Standard Time)

This issue is resolved.
Need to use truffle unbox webpack instead of truffle init webpack.

@Gandalf-Pl @FabiolaBusch @JimiPedros

Vilayhong Bounthanh · Answer 19 · Wed May 30 2018 12:43:44 GMT+0800 (China Standard Time)

@cmaliwal It's not working.
truffle unbox webpack
this occurs below error.
Compilation warnings encountered:

/F/ETHERIUM/my-money/contracts/MetaCoin.sol:15:2: Warning: Defining constructors as functions with the same name as the contract is deprecated. Use "constructor(...) { ... }" instead.
function MetaCoin() public {
^ (Relevant source part starts here and spans across multiple lines).
,/F/ETHERIUM/my-money/contracts/Migrations.sol:11:3: Warning: Defining constructors as functions with the same name as the contract is deprecated. Use "constructor(...) { ... }" instead.
function Migrations() public {
^ (Relevant source part starts here and spans across multiple lines).
,/F/ETHERIUM/my-money/contracts/MetaCoin.sol:23:3: Warning: Invoking events without "emit" prefix is deprecated.
Transfer(msg.sender, receiver, amount);
^------------------------------------^

Writing artifacts to .\build\contracts

Could not connect to your Ethereum client. Please check that your Ethereum client:
- is running
- is accepting RPC connections (i.e., "--rpc" option is used in geth)
- is accessible over the network
- is properly configured in your Truffle configuration file (truffle.js)

F:\ETHERIUM\my-money>truffle.cmd serve

Serving static assets in .\build on port 8080...
TypeError: fsevents is not a constructor
at createFSEventsInstance (C:\Users\ediso\AppData\Roaming\npm\node_modules\truffle\build\webpack:~\chokidar\lib\fsevents-handler.js:26:1)
at setFSEventsListener (C:\Users\ediso\AppData\Roaming\npm\node_modules\truffle\build\webpack:~\chokidar\lib\fsevents-handler.js:80:1)
at FSWatcher.FsEventsHandler._watchWithFsEvents (C:\Users\ediso\AppData\Roaming\npm\node_modules\truffle\build\webpack:~\chokidar\lib\fsevents-handler.js:244:1)
at FSWatcher. (C:\Users\ediso\AppData\Roaming\npm\node_modules\truffle\build\webpack:~\chokidar\lib\fsevents-handler.js:378:1)
at LOOP (fs.js:1773:14)
at _combinedTickCallback (internal/process/next_tick.js:73:7)
at process._tickCallback (internal/process/next_tick.js:104:9)

ChiragMaliwal · Answer 20 · Wed May 30 2018 17:14:49 GMT+0800 (China Standard Time)

Disable the FsEvents when not used:

C:\Users\ediso\AppData\Roaming\npm\node_modules\truffle\build\cli.bundled.js

// if (!FsEventsHandler.canUse())

opts.useFsEvents = false;

Steps:

truffle compile && truffle build && truffle migrate && truffle serve

Roman Glushko · Answer 21 · Fri Aug 03 2018 19:45:53 GMT+0800 (China Standard Time)

The same issue for running truffle serve installed on level of project (not globally):

Docker

Based on Image:
node:8.0.0-alpine
Truffle Version:
Truffle v4.1.13 (core: 4.1.13)
Solidity v0.4.24 (solc-js)

OS X

System Version:
High Sierra 10.13.3 (17D47)
Node Versions:
v8.11.3
Truffle Version:
Truffle v4.1.13 (core: 4.1.13)
Solidity v0.4.24 (solc-js)

Also, I could not manage to use webpack box running truffle unbox webpack I get (on mentioned docker env):

Downloading...
Unpacking...
Setting up...
Error: stdout maxBuffer exceeded
at Socket.onChildStdout (child_process.js:328:14)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at addChunk (_stream_readable.js:263:12)
at readableAddChunk (_stream_readable.js:246:13)
at Socket.Readable.push (_stream_readable.js:208:10)
at Pipe.onread (net.js:597:20)

Issue has been already spotted for other box:
truffle-box/react-box#56

@tcoulter can you please address this?

Salman Hasan · Answer 22 · Wed Dec 26 2018 15:35:46 GMT+0800 (China Standard Time)

same problem not solve...........
truffle serveServing static assets in ./build on port 8080...

/usr/local/lib/node_modules/truffle/build/webpack://chokidar/lib/fsevents-handler.js:26
return (new fsevents(path)).on('fsevent', callback).start();
^
TypeError: fsevents is not a constructor
at createFSEventsInstance (/usr/local/lib/node_modules/truffle/build/webpack://chokidar/lib/fsevents-handler.js:26:1)
at setFSEventsListener (/usr/local/lib/node_modules/truffle/build/webpack://chokidar/lib/fsevents-handler.js:80:1)
at FSWatcher.FsEventsHandler._watchWithFsEvents (/usr/local/lib/node_modules/truffle/build/webpack://chokidar/lib/fsevents-handler.js:244:1)
at FSWatcher. (/usr/local/lib/node_modules/truffle/build/webpack:/~/chokidar/lib/fsevents-handler.js:378:1)
at gotStat (fs.js:1783:21)
at FSReqWrap.oncomplete (fs.js:152:21)

Salman Hasan · Answer 23 · Wed Dec 26 2018 15:43:46 GMT+0800 (China Standard Time)

truffle unboxwebpack
Downloading...
Error: Something already exists at the destination. truffle init and truffle unbox must be executed in an empty folder. Stopping to prevent overwriting data.
at /usr/local/lib/node_modules/truffle/build/webpack:/packages/truffle-box/lib/utils/unbox.js:22:1
at
at process._tickCallback (internal/process/next_tick.js:188:7)
at Function.Module.runMain (module.js:695:11)
at startup (bootstrap_node.js:188:16)
at bootstrap_node.js:609:3

Kevin Nørby Andersen · Answer 24 · Mon Jul 11 2022 04:52:38 GMT+0800 (China Standard Time)

I got the same error on truffle v5.5.21 running on node v16.15.1. When digging into it, I got a warning that fsevents could be breaking.
npm install npm WARN old lockfile npm WARN old lockfile The package-lock.json file was created with an old version of npm, npm WARN old lockfile so supplemental metadata must be fetched from the registry. npm WARN old lockfile npm WARN old lockfile This is a one-time fix-up, please be patient... npm WARN old lockfile npm WARN deprecated fsevents@1.2.4: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.

I changed my package.json file to use the latest version of lite-server and now it works for me.