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.

Sign up for GitHub

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

Jump to bottom

Can't resolve 'encoding' warning when using picosanity in Next.js 13 client components #19

Open

thobas-dnvgl opened this issue Mar 10, 2023 · 1 comment

thobas-dnvgl commented Mar 10, 2023 •

edited

Loading

When using picosanity in a client component in Next.js 13 app dir I get this warning:

Module not found: Can't resolve 'encoding' in 'C:\Users\THOBAS\Code\next-13-1\node_modules\node-fetch\lib'

Import trace for requested module:
./node_modules/node-fetch/lib/index.js
./node_modules/picosanity/lib/index.js
./lib/sanity.ts
./app/HomePage.tsx

It's just a warning, everything works.

According to supabase/supabase-js#612, it's due to an old version of node-fetch. Any drawback in updating picosanity dependencies? :)

The text was updated successfully, but these errors were encountered:

roch-numbered commented Mar 27, 2023

+1
Same problem for me 👋

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment