Starting a Vaadin 16 app with Node 14 on Mac prints 1172 error lines
See original GitHub issuevaadin init --pre test16
cd test16
mvn
2020-05-27 15:43:15.669 INFO 37473 --- [nPool-worker-19] com.vaadin.flow.server.DevModeHandler : Started webpack-dev-server. Time: 8375ms
(node:37536) UnhandledPromiseRejectionWarning: TypeError: fsevents.watch is not a function
at createFSEventsInstance (/Users/artur/tmp/tst-16/node_modules/.pnpm/registry.npmjs.org/chokidar/3.4.0/node_modules/chokidar/lib/fsevents-handler.js:93:25)
at setFSEventsListener (/Users/artur/tmp/tst-16/node_modules/.pnpm/registry.npmjs.org/chokidar/3.4.0/node_modules/chokidar/lib/fsevents-handler.js:148:16)
at FsEventsHandler._watchWithFsEvents (/Users/artur/tmp/tst-16/node_modules/.pnpm/registry.npmjs.org/chokidar/3.4.0/node_modules/chokidar/lib/fsevents-handler.js:352:18)
at FsEventsHandler.initWatch (/Users/artur/tmp/tst-16/node_modules/.pnpm/registry.npmjs.org/chokidar/3.4.0/node_modules/chokidar/lib/fsevents-handler.js:429:23)
at FsEventsHandler._addToFsEvents (/Users/artur/tmp/tst-16/node_modules/.pnpm/registry.npmjs.org/chokidar/3.4.0/node_modules/chokidar/lib/fsevents-handler.js:518:12)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:37536) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:37536) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:37536) UnhandledPromiseRejectionWarning: TypeError: fsevents.watch is not a function
at createFSEventsInstance (/Users/artur/tmp/tst-16/node_modules/.pnpm/registry.npmjs.org/chokidar/3.4.0/node_modules/chokidar/lib/fsevents-handler.js:93:25)
at setFSEventsListener (/Users/artur/tmp/tst-16/node_modules/.pnpm/registry.npmjs.org/chokidar/3.4.0/node_modules/chokidar/lib/fsevents-handler.js:148:16)
at FsEventsHandler._watchWithFsEvents (/Users/artur/tmp/tst-16/node_modules/.pnpm/registry.npmjs.org/chokidar/3.4.0/node_modules/chokidar/lib/fsevents-handler.js:352:18)
at FsEventsHandler.initWatch (/Users/artur/tmp/tst-16/node_modules/.pnpm/registry.npmjs.org/chokidar/3.4.0/node_modules/chokidar/lib/fsevents-handler.js:429:23)
at FsEventsHandler._addToFsEvents (/Users/artur/tmp/tst-16/node_modules/.pnpm/registry.npmjs.org/chokidar/3.4.0/node_modules/chokidar/lib/fsevents-handler.js:518:12)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
...
Most probably related to #8278
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Error "Failed to determine 'node' tool." with new Vaadin 14.0.0 ...
A new project was downloaded to my Mac (Mojave). I opened the project with IntelliJ Ultimate edition version 2019.2, and waiting a while...
Read more >maven - New Vaadin 14 app fails to run, error ... - Stack Overflow
Starting from versions 14.2 and 16, the Node.js install (which includes npm) happens automatically. It is installed to a .vaadin folder ...
Read more >Untitled
Lea michele matthew morrison, Famous time capsule openings, North node in aries ... Birds flying around head app, Upload dropbox photos to google...
Read more >GWT Release Notes
Add support to compile GWT itself in Java 9+. Improve compiled code size for applications that never use streams, by avoiding referencing streams...
Read more >Untitled
Burbank amc 16 prime, 4651 sheridan street suite 335 hollywood fl, ... Detective conan movie 14 animeultima, German international team starting 11, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Apparent workaround:
you are right. I don’t know what happened but now the page is working fine. I think that was a problem with the deploy process form Now side. thank you very much @Artur- !!