Open chaffeqa opened 4 months ago
2 & 3 will need to be fixed with peer versions I'm afraid, as the graphiql-code-exporter
itself is third party, our module is @graphiql/plugin-code-exporter and implements this library
Ah figured it out: So the example is referencing a UMD compiled version (which bundles in graphiql-code-exporter
, hence why I was confused).
The issue is: it looks like the Babel regenerator-runtime
is no longer included in any of the other previous scripts (react, react-dom, graphiql). Simply adding the script import fixes the issue:
<!DOCTYPE html>
<html>
<head>
<title>Sample - GraphiQL</title>
<link href="https://unpkg.com/graphiql/graphiql.min.css" rel="stylesheet" />
<link href="https://unpkg.com/@graphiql/plugin-code-exporter/dist/style.css" rel="stylesheet" />
<script crossorigin src="https://unpkg.com/regenerator-runtime@0.14.1/runtime.js"></script>
<script crossorigin src="https://unpkg.com/react@18/umd/react.production.min.js"></script>
<script crossorigin src="https://unpkg.com/react-dom@18/umd/react-dom.production.min.js"></script>
<script crossorigin src="https://unpkg.com/graphiql/graphiql.min.js"></script>
<script crossorigin src="https://unpkg.com/@graphiql/plugin-code-exporter/dist/index.umd.js"></script>
</head>
</html>
fantastic! i forget why we hadn't removed that long ago, what an artefact 😂 we need to have some script type module examples as well, it's 2024 c'mon 😂!!
Ok been diving even deeper now that I have this working:
I believe it would be in the communities best intirest to figure out how to move forward with this plugin. Maybe ask @mtrythall (who was the last committer) what their use is, whether that repo should be the community standard, or if it should be merged into this mono-repo?
Is there an existing issue for this?
Current Behavior
When I try to use the CDN approach for any of the plugins, I run into the following issues:
Expected Behavior
Working example files in the plugins
Steps To Reproduce
No response
Environment
react
Version:graphql
Version:Anything else?
Guessing this may just simply be that 3.0.3 is not published to the CDN?