Better developer documentation
See original GitHub issueAfter cloning this repository and changing directory to packages/examples/graphiql-webpack/
and running npm run demo-build
, the build fails with
Error: Cannot find module '@babel/core'
babel-loader@8 requires Babel 7.x (the package '@babel/core'). If you'd like to use Babel 6.x ('babel-core'), you should install 'babel-loader@7'.
Adding @babel/core
(currently version 7.7.4
) to devDependencies
solved the problem for me. Let me know if you want me to create a PR with this change.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:19 (13 by maintainers)
Top Results From Across the Web
9 Components of Great Developer and API Documentation
Creating great developer documentation is harder than it looks. Learn from Stripe, Twilio, GitHub, and more to learn how you can create docs...
Read more >8 Great Examples of Developer Documentation
Good documentation allows feedback from readers so they can point out inconsistencies or typos and have them addressed quickly. Even better is ...
Read more >Docs for Developers – Documentation for Everyone
Docs for Developers demystifies the process of creating great developer documentation, following a team of software developers as they work to launch a...
Read more >Building Better Documentation Practices for Developers, ...
Developers care about docs and will pass up working on an open source project because it lacks good documentation. Learn more.
Read more >Developer Documenting Done Right: Why, Who, What, ...
1. Good documentation makes dev teams more productive · 2. Documentation contributes to building strong team cultures · 3. Code documentation is ...
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
Success!
This was user error. I remember running
yarn build-bundles
per the docs, but at some point I think I started over (withgit clean ...
) and didn’t rerunyarn build-bundles
before trying to build the webpack example.I’m good to go. Thanks for being so responsive.
Oops 😅
In my day-to-day I actually use
git clean -ixd
for the interactive version that lets me exclude certain patterns from removal.Lastly, kudos again for this project.
In my view, GraphiQL is a huge contributor to graphql adoption in the industry and here at Netflix. I’m working on shipping a graphql endpoint for Netflix/hollow datastores. Being able to ship a query UI & IDE alongside it is so useful.
It has already given me agility while developing the endpoint. Not only do I think users will appreciate having GraphiQL, but I think it’s an expectation now. Several other services here are already in PROD with vanilla/reference GraphiQL UIs deployed.