Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

easygraphql-firebase failed #6

Open
louishugens opened this issue May 29, 2019 · 0 comments
Open

easygraphql-firebase failed #6

louishugens opened this issue May 29, 2019 · 0 comments

Comments

@louishugens
Copy link

Hello
The command failed with the below:

Error: Cannot read property 'fields' of undefined
(node:11400) UnhandledPromiseRejectionWarning: AssertionError [ERR_ASSERTION]: rimraf: missing path
at Object.rimrafSync [as removeSync] (C:\Users\Hugens\AppData\Roaming\npm\node_modules\easygraphql-firebase\node_modules\fs-extra\lib\remove\rimraf.js:231:3)
at handleResponse (C:\Users\Hugens\AppData\Roaming\npm\node_modules\easygraphql-firebase\commands\start.js:112:8)
at process._tickCallback (internal/process/next_tick.js:68:7)
at Function.Module.runMain (internal/modules/cjs/loader.js:745:11)
at startup (internal/bootstrap/node.js:283:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:743:3)
(node:11400) 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(). (rejection id: 2)
(node:11400) [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.

Do i need to init firebase or something?

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

No branches or pull requests

1 participant