Skip to content

Master fails to install graphql-playground #1131

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

Closed
acinader opened this issue Jul 8, 2019 · 5 comments · Fixed by #1133
Closed

Master fails to install graphql-playground #1131

acinader opened this issue Jul 8, 2019 · 5 comments · Fixed by #1133

Comments

@acinader
Copy link
Contributor

acinader commented Jul 8, 2019

@douglasmuraoka

I'm trying to put together a release to get your awesome fix and new feature out.

When I try to do a clean install on master I get this error:

npm ERR! Could not install from "node_modules/graphql-playground-react/codemirror-graphql@github:timsuchanek/codemirror-graphql#801ec32683c38d6dc0f8f7bc19014a111edc9ebd" as it does not contain a package.json file.

I opened an issue on the graphql-playground repo:

graphql/graphql-playground#1052

I'll close this and release when resolved.

@douglasmuraoka
Copy link
Contributor

@acinader looks like the problem was the package-lock. I've just created a brand new file and it is working now.

@acinader
Copy link
Contributor Author

any interest in putting together the release?

@douglasmuraoka
Copy link
Contributor

@acinader do you have some guideline to follow when launching new releases?

@acinader
Copy link
Contributor Author

acinader commented Jul 11, 2019

nothing formal, but it is pretty straight forward:

I think this should be 1.4.0 because we are adding non-breaking functionality

  • create a pull request to get things ready
  1. View the full changelog and update the CHANGELOG.md file
  2. Set the version in package.json and then run npm install to generate the lock file
  • Use github to create the release once the above pr is merged. When creating the release with the github ui, follow the format of previous releases. When you publish the release, travis will deploy it to npm (you can see the .travis.yml file to see how that is configured).

If you screw up somehow, don't sweat it, we can just do another release to fix anything.

Good luck!

@TomWFox fyi.

@douglasmuraoka
Copy link
Contributor

@acinader @TomWFox pull request created #1134

beiguancyc pushed a commit to beiguancyc/parse-dashboard that referenced this issue Jul 13, 2019
* parse: (21 commits)
  Reset credentials (parse-community#1135)
  1.4.0 version bump + changelog (parse-community#1134)
  Fix: Master fails to install graphql-playground parse-community#1131 (parse-community#1133)
  Update eslint-plugin-react to the latest version 🚀 (parse-community#1122)
  Update babel7 to the latest version 🚀 (parse-community#1129)
  GraphQL API playground (parse-community#1123)
  Fix: Can't switch (dropdown list) between servers parse-community#1045 (parse-community#1125)
  Update puppeteer to the latest version 🚀 (parse-community#1124)
  Update eslint-plugin-react to the latest version 🚀 (parse-community#1120)
  Update webpack-cli to the latest version 🚀 (parse-community#1119)
  Update react-dnd to the latest version 🚀 (parse-community#1117)
  Update puppeteer to the latest version 🚀 (parse-community#1116)
  Update react-dnd to the latest version 🚀 (parse-community#1114)
  Update babel-eslint to the latest version 🚀 (parse-community#1113)
  Update react-dnd to the latest version 🚀 (parse-community#1111)
  Update react-dnd to the latest version 🚀 (parse-community#1110)
  Update package-json to the latest version 🚀 (parse-community#1108)
  Update webpack-cli to the latest version 🚀 (parse-community#1106)
  Update react-dnd to the latest version 🚀 (parse-community#1104)
  Update webpack-cli to the latest version 🚀 (parse-community#1103)
  ...

# Conflicts:
#	package-lock.json
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants