Skip to content
This repository has been archived by the owner on Sep 2, 2022. It is now read-only.

bad dependency requests an upgrade of graceful-fs #3274

Closed
tianhuil opened this issue Oct 9, 2018 · 1 comment
Closed

bad dependency requests an upgrade of graceful-fs #3274

tianhuil opened this issue Oct 9, 2018 · 1 comment
Labels
area/cli status/stale Marked as state by the GitHub stalebot

Comments

@tianhuil
Copy link

tianhuil commented Oct 9, 2018

Describe the bug
When installing the latest version of primsa, I get the following error:

warning prisma > prisma-cli-core > prisma-generate-schema > prisma-cli > prisma-cli-core > unzip > fstream > [email protected]: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js

This is using the following package.json dependencies

{
  "dependencies": {
    "graphql": "0.13",
    "graphql-yoga": "^1.16.2",
    "prisma-binding": "^2.1.6",
    "prisma-client-lib": "^1.17.1"
  },
  "devDependencies": {
    "graphql-cli": "^2.16.7",
    "nodemon": "^1.18.4",
    "prisma": "^1.17.1",
    "ts-node": "^7.0.1",
    "typescript": "^3.1.1"
  }
}

To Reproduce
Follow the instructions in this repo.

Expected behavior
For there not to be any errors.

Versions (please complete the following information):

  • The error occurs in the node:8.12-alpine docker container.

Proposed Solution:
This issue has been documented in the unzip library, which has not been updated since September of 2014. It is recommended that we upgrade to unzip-stream, which is a fork that fixes the graceful-fs dependency, amongst other things.

@stale
Copy link

stale bot commented Nov 23, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the status/stale Marked as state by the GitHub stalebot label Nov 23, 2018
@stale stale bot closed this as completed Dec 3, 2018
@pantharshit00 pantharshit00 added area/cli status/stale Marked as state by the GitHub stalebot labels Jan 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/cli status/stale Marked as state by the GitHub stalebot
Projects
None yet
Development

No branches or pull requests

3 participants