You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've tried creating fresh vite and webpack projects and then following the installation instructions here, but the editor does not appear to be working. I get this error in the console: "forwardRef render functions accept exactly two parameters: props and ref". I am using version 6.8.2 but have tried 6.6.5, 6.7.0, and 6.8.0 as well.
Reproduce:
Create a fresh vite or webpack project, I used: https://www.npmjs.com/package/create-vite with the React/typescript options
Follow the installation instructions on this Github project and add the example code to your App.tsx/js
The text was updated successfully, but these errors were encountered:
Is there any way to run graphql-editor with vite+react... I am receiving issues with both vite, vitest commands.
with vite command
GET http://localhost:5173/@fs/****/node_modules/.vite/deps/validation.worker.js?type=classic&worker_file 504 (Outdated Optimize Dep)
with vitest command
Module <project_path>/node_modules/graphql-editor-worker/lib/index.js:1 seems to be an ES Module but shipped in a CommonJS package. You might want to create an issue to the package "graphql-editor-worker" as
king them to ship the file in .mjs extension or add "type": "module" in their package.json.
I've tried creating fresh vite and webpack projects and then following the installation instructions here, but the editor does not appear to be working. I get this error in the console: "forwardRef render functions accept exactly two parameters: props and ref". I am using version 6.8.2 but have tried 6.6.5, 6.7.0, and 6.8.0 as well.
Reproduce:
Create a fresh vite or webpack project, I used: https://www.npmjs.com/package/create-vite with the React/typescript options
Follow the installation instructions on this Github project and add the example code to your App.tsx/js
The text was updated successfully, but these errors were encountered: