Can't Resolve "encoding" Module Error While Using Nextjs-13 + Supabase

Question

I'm trying to use Supabase for inserting/collecting data from my form. But when I compile I got encoding module is not found error. I already tried cache cleaning and re-installing npm modules. They didn't work either.

Project Structure:

apply/page.tsx Code:

"use client"
import { supabase } from "lib/supabaseClient"

export default function Apply() {

    // This function called by button so we use "use client" at top.
    async function createApplyRecord() {
        const { error } = await supabase
            .from('applications')
            .insert({id: 1, fullname: "test", email: "aa", phone: "bb", githuburl: "cc", linkedinurl: "dd", about: "ee"})
            console.log("inserted")
            if(error) {
                console.log(error);
            }
    }

  return (SOME HTML CODE HERE)
}

Error I Got:

Shot in the dark but maybe your node version is off? Might be worth updating it to the latest version. — dshukertjr, Feb 15 '23 at 07:06
Its up to date. I'm tried at LTS and Experimental versions. None of them changes anything. — Poyraz HANCILAR, Feb 15 '23 at 21:15

score 25 · Accepted Answer · answered Feb 20 '23 at 03:10

25

This is just a warning that can be safely ignored. We're working on removing it. You can follow along here: https://github.com/supabase/supabase-js/issues/612

answered Feb 20 '23 at 03:10

thorwebdev

818
4
9

1

Any case you know how to tell vercel to NOT treat this warning as error? My deploy is failing because of this. edit: found it https://vercel.com/guides/how-do-i-resolve-a-process-env-ci-true-error – Tasos Tsournos Mar 11 '23 at 17:52
3

@TasosTsournos remove the error for now using: npm i -D encoding – Richard Torcato May 12 '23 at 13:58
npm i -D encoding does the trick – Jonathan Laliberte Aug 31 '23 at 18:05

score 6 · Answer 2 · answered Jun 24 '23 at 23:54

6

To fix this, I ran npm install encoding and the error was gone!

answered Jun 24 '23 at 23:54

Igor Stepanov

69
1
2

score 3 · Answer 3 · answered Jul 14 '23 at 01:42

I used a simple solution which was to use

npm i -D encoding

But the supabase community should have already solved this problem. However, they changed the authentication mode with the new versions of next 13. Which is a serious problem because I didn't want to have to redo the authentication of my project.

Can't Resolve "encoding" Module Error While Using Nextjs-13 + Supabase

3 Answers3

Linked