forked from brentvatne/nodevember-2017-mobile
-
Notifications
You must be signed in to change notification settings - Fork 14
Open
Labels
bugSomething isn't workingSomething isn't working
Description
The error:
web Starting Webpack on port 19006 in development mode.
(node:7716) UnhandledPromiseRejectionWarning: ValidationError: webpack Dev Server Invalid Options
options should NOT have additional properties
at validateOptions (/home/plpp-2019/.config/yarn/global/node_modules/schema-utils/src/validateOptions.js:32:11)
at new Server (/home/plpp-2019/.config/yarn/global/node_modules/webpack-dev-server/lib/Server.js:87:5)
at server (/@expo/[email protected]/src/Webpack.ts:160:20)
at new Promise (<anonymous>)
at startAsync (/@expo/[email protected]/src/Webpack.ts:149:18)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at Object.openAsync (/@expo/[email protected]/src/Webpack.ts:203:5)
at ReadStream.handleKeypress (/[email protected]/src/commands/start/TerminalUI.js:237:9)
(node:7716) 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: 16)
(node:7716) [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.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working