Uncaught ReferenceError: exports is not defined #71

batamire · 2020-11-05T10:50:58Z

trying to:

import { zodResolver } from "@hookform/resolvers/zod";

gives me:

Uncaught ReferenceError: exports is not defined
    at Module../node_modules/@hookform/resolvers/dist/zod.js (zod.js:11)
    at __webpack_require__ (bootstrap:789)
    at fn (bootstrap:100)
    at Object../node_modules/@hookform/resolvers/zod.js (zod.js:1)
    at __webpack_require__ (bootstrap:789)
    at fn (bootstrap:100)
    ...

This is a Rails webpacker + typescript app.

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

bluebill1049 · 2020-11-05T10:53:39Z

more detail... which version and etc... can you reproduce that in CSB?

batamire · 2020-11-05T10:59:43Z

@hookform/resolvers": "^1.0.0"

I'm afraid I cannot reproduce it as this is a large Rails app with TypeScript React and GraphQL. Could it be the way you export modules? I really lack JS packaging knowledge...

my babel.config.js:

module.exports = function(api) {
  var validEnv = ["development", "test", "production"];
  var currentEnv = api.env();
  var isDevelopmentEnv = api.env("development");
  var isProductionEnv = api.env("production");
  var isTestEnv = api.env("test");

  if (!validEnv.includes(currentEnv)) {
    throw new Error(
      "Please specify a valid `NODE_ENV` or " +
        '`BABEL_ENV` environment variables. Valid values are "development", ' +
        '"test", and "production". Instead, received: ' +
        JSON.stringify(currentEnv) +
        "."
    );
  }

  return {
    presets: [
      isTestEnv && [
        "@babel/preset-env",
        {
          targets: {
            node: "current"
          },
          modules: "commonjs"
        },
        "@babel/preset-react"
      ],
      (isProductionEnv || isDevelopmentEnv) && [
        "@babel/preset-env",
        {
          forceAllTransforms: true,
          useBuiltIns: "entry",
          corejs: 3,
          modules: false,
          exclude: ["transform-typeof-symbol"]
        }
      ],
      [
        "@babel/preset-react",
        {
          development: isDevelopmentEnv || isTestEnv,
          useBuiltIns: true
        }
      ],
      ['@babel/preset-typescript', { 'allExtensions': true, 'isTSX': true }]
    ].filter(Boolean),
    plugins: [
      "babel-plugin-macros",
      "@babel/plugin-syntax-dynamic-import",
      isTestEnv && "babel-plugin-dynamic-import-node",
      "@babel/plugin-transform-destructuring",
      [
        "@babel/plugin-proposal-class-properties",
        {
          loose: true
        }
      ],
      [
        "@babel/plugin-proposal-object-rest-spread",
        {
          useBuiltIns: true
        }
      ],
      [
        "@babel/plugin-transform-runtime",
        {
          helpers: false,
          regenerator: true,
          corejs: false
        }
      ],
      [
        "@babel/plugin-transform-regenerator",
        {
          async: false
        }
      ],
      isProductionEnv && [
        "babel-plugin-transform-react-remove-prop-types",
        {
          removeImport: true
        }
      ]
    ].filter(Boolean)
  };
};

tsconfig.json

{
  "compilerOptions": {
    "declaration": false,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "lib": ["es6", "dom"],
    "module": "commonjs",
    "moduleResolution": "node",
    "sourceMap": true,
    "target": "es5",
    "jsx": "react",
    "allowSyntheticDefaultImports": true,
    "noEmit": true,
    "noImplicitAny": true,
    "noImplicitThis": true,
    "noImplicitReturns": true,
    "strictNullChecks": true
  },
  "exclude": ["**/*.spec.ts", "node_modules", "public"],
  "compileOnSave": false
}

jorisre · 2020-11-05T18:05:46Z

@batamire Hi 👋🏻

Does that error occur at build time ?

Can you provide more informations please ?
Your code snippets doesn't help me :/

sfederowicz · 2020-11-05T19:39:51Z

I'm running into that same runtime error (also using Rails + webpacker but no Typescript). I'm importing the yup resolver rather than the zod resolver, but it's the same error otherwise.

My Babel config is identical to the one posted above, excluding only the Typescript preset line (since we don't use Typescript):
['@babel/preset-typescript', { 'allExtensions': true, 'isTSX': true }]

Issue occurs when using the 1.0.0 or 2.0.0-rc.1 version of the lib but didn't occur with the 0.1.1 or 0.2.0-beta.12.

Adding this plugin to Babel fixes the issue and prevents the runtime error from being thrown:
@babel/plugin-transform-modules-commonjs

Unfortunately, adding that plugin also causes a different runtime errors to be thrown for me in some Rails-related JS code (code that is unrelated to react-hook-form), so that alone likely won't be your panacea. Still trying to figure out how to get around this since I'm not great with webpack.

batamire · 2020-11-05T21:33:31Z

It builds without problems, the error is pasted from Chrome Devtools, happens on component mount...

Uncaught ReferenceError: exports is not defined

Offending line:

Object.defineProperty(exports, "__esModule", {
  value: true
});

@sfederowicz same thing happens with yup...

studnik18 · 2020-11-10T11:00:22Z

Up for yup...

bluebill1049 · 2020-11-16T21:38:09Z

Is this still an issue for everyone? (i couldn't reproduce)

studnik18 · 2020-11-17T14:42:17Z

Yes. Can't update from 0.0.6 because of it. My most relevant dependencies:
"react": "^17.0.1", "react-hook-form": "^6.11.0", "@hookform/resolvers": "^0.0.6", "yup": "^0.29.3", "@rails/webpacker": "^5.2.1", "react-on-rails": "^12.0.3"

bluebill1049 · 2020-11-17T22:10:42Z

@studnik18 have you try to upgrade to the latest? and what build tool are you using?

studnik18 · 2020-11-18T10:33:20Z

Yes, I tried just before posting :) Our setting is quite complicated - it's a monorepo with rails 6 and webpacker as ruby gems, on the frontend side it's @rails/webpacker 5.2.1 which features webpack 4.x.x according to the docs (no TypeScript).

brentmulligan · 2020-12-04T21:42:12Z

Having the same issue, also using rails/webpacker. Downgrading to 0.1.1 did resolve.

johnandresmedina · 2020-12-07T00:06:06Z

I was having the same issue, I tried to replicate it in codesandbox with no luck and after spending some more time it turned out to be a reference to the old way of importing the package: @hookform/resolvers instead of @hookform/resolvers/yup, so you might want to check all the references.

studnik18 · 2020-12-07T08:55:31Z

I had this lightbulb moment too :) But unfortunately that solution alone didn't help. Thanks anyway John.

ramaboo · 2020-12-14T12:14:35Z

Getting this too for yup import { yupResolver } from "@hookform/resolvers/yup"; on a Rails 6.1 project

jorisre · 2020-12-14T13:07:14Z

Thanks for reporting, I'm looking for a solution

YimingIsCOLD · 2020-12-23T22:03:13Z

I am getting this too for yup on a non-rails project. I am only getting the error on production build and not in development build.

Edit: after adding sourceType: 'unambiguous' into babel.config.js, I am able to resolve the runtime error. The issue might be webpack/webpack#4039 (comment).

jorisre · 2020-12-31T08:10:55Z

Hi all, the last version 1.3.1 should fix this issue, someone can confirm ? Thanks

amankkg · 2020-12-31T13:32:44Z

@jorisre 1.3.1 using snowpack on import {zodResolver} from '@hookform/resolvers/zod throws following error

SyntaxError: The requested module '../../web_modules/@hookform/resolvers/zod.js' does not provide an export named 'zodResolver'

jorisre · 2020-12-31T13:36:25Z

@amankkg thank for your feedbacks. Could you provide a snowpack example please ?

ℹ️ I'm working on resolvers v2 with a better module support

amankkg · 2020-12-31T13:57:19Z

@jorisre hmm on 1.3.0 it works properly

here is my WIP https://github.com/amankkg/frontend-template

amankkg · 2020-12-31T14:07:49Z

@jorisre it is quite messy 😅 let me know if you need clear and stable reproduction repo

amankkg · 2021-01-05T07:12:42Z

My case is fixed with 1.4.0-beta.1

jorisre · 2021-01-05T13:05:47Z

@amankkg I'm glad it solves your problem ! :) But 1.4.0-beta.1 was a mistake with semantic-release. Please use 2.0.0-beta.3 instead.

Next.js's users have the same problem since 1.3.1 : #100
Workaround possible: use the v1.3.0 or try the v2 beta

EDIT (2/1/2020): Same for Snowpack users

For everyone which want to try the v2, you can install the @hookform/resolvers@beta, at this time the beta.3 contains:

A TypeScript fix for Yup
A better modules support (without breaking changes)

Feedbacks are really appreciated :) If some of you get some errors with modules, please reply here.

MontoyaAndres · 2021-01-24T22:26:23Z

I'm facing the same issue as #100 ,

andres@andres:~/Entrepreneurship/TeVi$ yarn build

yarn run v1.22.10
$ next build
Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db
info  - Using external babel configuration from /home/andres/Entrepreneurship/TeVi/.babelrc
info  - Creating an optimized production build  
info  - Compiled successfully

> Build error occurred
/home/andres/Entrepreneurship/TeVi/node_modules/@hookform/resolvers/dist/yup.js:2
import { transformToNestObject } from 'react-hook-form';
^^^^^^

SyntaxError: Cannot use import statement outside a module
    at wrapSafe (internal/modules/cjs/loader.js:979:16)
    at Module._compile (internal/modules/cjs/loader.js:1027:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
    at Module.load (internal/modules/cjs/loader.js:928:32)
    at Function.Module._load (internal/modules/cjs/loader.js:769:14)
    at Module.require (internal/modules/cjs/loader.js:952:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at Object.<anonymous> (/home/andres/Entrepreneurship/TeVi/node_modules/@hookform/resolvers/yup.js:1:18)
    at Module._compile (internal/modules/cjs/loader.js:1063:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10) {
  type: 'SyntaxError'
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Now, I can't deploy to vercel :(

The versions I'm using are:

    "@hookform/resolvers": "^1.2.0",
    "next": "^10.0.4",
    "react": "^17.0.1",
    "react-dom": "^17.0.1",
    "react-hook-form": "^6.13.1",
    "yup": "^0.32.8"

MontoyaAndres · 2021-01-24T22:33:41Z

Also, I updated to "@hookform/resolvers": "1.3.2" and I get the same error...

bluebill1049 · 2021-01-24T22:35:08Z

@MontoyaAndres try to use the latest beta version.

MontoyaAndres · 2021-01-24T22:38:48Z

@bluebill1049 Works great! Thank you so much! I was deploying normally to Vercel when that error appears surprisingly 🤔🤔🤔.

bluebill1049 · 2021-01-24T22:40:02Z

@bluebill1049 Works great! Thank you so much! I was deploying normally to Vercel when that error appears surprisingly 🤔🤔🤔.

not sure about that :( sounds like picking update the latest, but your package.json says another story. (pick up the latest patch)

MontoyaAndres · 2021-01-24T22:42:58Z

Very strange, I didn't update anything in my code about react-hook-form... Just appeared when the building was executing in Vercel :(

asotog · 2021-01-27T14:17:24Z

@amankkg I'm glad it solves your problem ! :) But 1.4.0-beta.1 was a mistake with semantic-release. Please use 2.0.0-beta.3 instead.

Next.js's users have the same problem since 1.3.1 : #100
Workaround possible: use the v1.3.0 or try the v2 beta

For everyone which want to try the v2, you can install the @hookform/resolvers@beta, at this time the beta.3 contains:

A TypeScript fix for Yup

A better modules support (without breaking changes)

Feedbacks are really appreciated :) If some of you get some errors with modules, please reply here.

This worked for me, thanx, when are you planning to release this version?

jorisre · 2021-01-27T14:19:40Z

@asotog At the same time of react-hook-form v7

@bluebill1049 Do we have a "deadline" ?

bluebill1049 · 2021-01-27T21:39:56Z

@asotog At the same time of react-hook-form v7

@bluebill1049 Do we have a "deadline" ?

No, we don't. It's open-source, we are all working on this in our free time. So no pressure, we get it right and we ship it out. I am planning to do a quick video to cover some of the major changes and improvements, then we can release a beta version and get more users to "test" this out.

borivojevic · 2021-01-30T18:23:13Z

I had the same issue with 1.3.2 using snowpack. 2.0.0-beta.3 didn't work either.

Although snowpack suggests this workaround that seems to be working for me:

// doesn't work
import { yupResolver } from '@hookform/resolvers/yup';

// it works
import type { yupResolver } from '@hookform/resolvers/yup';

borivojevic · 2021-01-31T13:23:48Z

Another workaround that works with snowpack v3.0.11 would be:

import hookforResolvers from '@hookform/resolvers/yup';
const yupResolver = hookforResolvers.yupResolver;

bluebill1049 · 2021-01-31T22:22:22Z

@jorisre any idea on this one above?

jorisre · 2021-02-01T10:31:25Z

It seems to work for @tajdien, can you share a working example please ?

@borivojevic I'm not familiar with Snowpack but if you have a reproductible example to provide then I can investigate thanks !

borivojevic · 2021-02-01T10:57:32Z

@jorisre I hope this example helps.

yarn install && yarn start should result in error.

This is the implementation that's problematic.

jorisre · 2021-02-01T11:13:22Z

@borivojevic Happy to try Snowpack, esbuild is fast as expected 🚀

In your example you use the version 1.3.3 which have an issue with module exports (solved in v2).
In your case, I recommend to use the 1.3.0 or try the v2 beta.
I get your example working with these both versions.

I added a note for Snowpack users : #71 (comment)

Hope it helps

borivojevic · 2021-02-01T11:22:16Z

Thanks @jorisre. I can confirm that v2 beta works on this smaller example as well.

WorldOfMaze · 2021-02-04T02:46:43Z

I was having this issue with yup and nextjs. After downgrading to 1.3.0, everything seems to be working OK. Thanks for the workaround @jorisre

hamzahasbi · 2021-02-28T18:50:17Z

using "@hookform/resolvers": "2.0.0-beta.3" with "next": "10.0.7" seems to work perfectly!
Thanks !

hawkcookie · 2021-03-02T07:04:46Z

using "@hookform/resolvers": "2.0.0-beta.3" with "next": "10.0.7" seems to work perfectly!

@hamzahasbi
It works well for me, thanks.

javierfuentesm · 2021-03-12T05:30:01Z

@amankkg I'm glad it solves your problem ! :) But 1.4.0-beta.1 was a mistake with semantic-release. Please use 2.0.0-beta.3 instead.

Next.js's users have the same problem since 1.3.1 : #100
Workaround possible: use the v1.3.0 or try the v2 beta

EDIT (2/1/2020): Same for Snowpack users

For everyone which want to try the v2, you can install the @hookform/resolvers@beta, at this time the beta.3 contains:

A TypeScript fix for Yup

A better modules support (without breaking changes)

Feedbacks are really appreciated :) If some of you get some errors with modules, please reply here.

It didnt work for me

javierfuentesm · 2021-03-12T05:32:29Z

using "@hookform/resolvers": "2.0.0-beta.3" with "next": "10.0.7" seems to work perfectly!

@hamzahasbi
It works well for me, thanks.

For me too !! :D

72636c · 2021-03-12T06:46:29Z

^1.3.0 will install the latest version >=1.3.0 <2.0.0. If you want to pin a specific version you should remove the caret ^.

iltonbarbosa · 2021-03-17T15:35:05Z

I have the same problem:

exports.__esModule = true;
^

ReferenceError: exports is not defined

jorisre · 2021-03-17T17:08:56Z

I have the same problem:

exports.__esModule = true;
^

ReferenceError: exports is not defined

#71 (comment)

jorisre · 2021-03-26T14:36:08Z

👋🏻
You can try the last version v1.3.6. The issue should be solved

decebal · 2021-09-09T22:39:43Z

1.3.9 seems to have the same issue again :(

studnik18 · 2021-09-10T10:26:30Z

There is 2.8.0 released. Why would you bother with 1.3.9 ?

decebal · 2021-09-10T12:59:07Z

thanks @studnik18 🙈 👍🏽

bluebill1049 added the question Further information is requested label Nov 5, 2020

jorisre mentioned this issue Dec 29, 2020

esm support to fix bundler incompatibility #95

Merged

jorisre mentioned this issue Jan 2, 2021

V2 - better modules support #104

Merged

jorisre mentioned this issue Jan 5, 2021

V2 🚀 #108

Merged

5 tasks

jorisre mentioned this issue Jan 5, 2021

Build error after upgrade to 1.3.1 in Next.js #100

Closed

jorisre added bug Something isn't working and removed question Further information is requested labels Jan 5, 2021

jorisre mentioned this issue Feb 20, 2021

SyntaxError: Cannot use import statement outside a module #107

Closed

jorisre closed this as completed Mar 28, 2021

Uncaught ReferenceError: exports is not defined #71

Uncaught ReferenceError: exports is not defined #71

Comments

batamire commented Nov 5, 2020

bluebill1049 commented Nov 5, 2020

batamire commented Nov 5, 2020

jorisre commented Nov 5, 2020 • edited Loading

sfederowicz commented Nov 5, 2020

batamire commented Nov 5, 2020

studnik18 commented Nov 10, 2020

bluebill1049 commented Nov 16, 2020 • edited Loading

studnik18 commented Nov 17, 2020

bluebill1049 commented Nov 17, 2020 • edited Loading

studnik18 commented Nov 18, 2020

brentmulligan commented Dec 4, 2020

johnandresmedina commented Dec 7, 2020

studnik18 commented Dec 7, 2020

ramaboo commented Dec 14, 2020

jorisre commented Dec 14, 2020

YimingIsCOLD commented Dec 23, 2020 • edited Loading

jorisre commented Dec 31, 2020

amankkg commented Dec 31, 2020

jorisre commented Dec 31, 2020

amankkg commented Dec 31, 2020

amankkg commented Dec 31, 2020

amankkg commented Jan 5, 2021

jorisre commented Jan 5, 2021 • edited Loading

MontoyaAndres commented Jan 24, 2021 • edited Loading

MontoyaAndres commented Jan 24, 2021

bluebill1049 commented Jan 24, 2021

MontoyaAndres commented Jan 24, 2021

bluebill1049 commented Jan 24, 2021

MontoyaAndres commented Jan 24, 2021

asotog commented Jan 27, 2021

jorisre commented Jan 27, 2021 • edited Loading

bluebill1049 commented Jan 27, 2021

borivojevic commented Jan 30, 2021 • edited Loading

borivojevic commented Jan 31, 2021

bluebill1049 commented Jan 31, 2021

jorisre commented Feb 1, 2021 • edited Loading

borivojevic commented Feb 1, 2021

jorisre commented Feb 1, 2021 • edited Loading

borivojevic commented Feb 1, 2021

WorldOfMaze commented Feb 4, 2021

hamzahasbi commented Feb 28, 2021

hawkcookie commented Mar 2, 2021 • edited Loading

javierfuentesm commented Mar 12, 2021

javierfuentesm commented Mar 12, 2021

72636c commented Mar 12, 2021

iltonbarbosa commented Mar 17, 2021

jorisre commented Mar 17, 2021

jorisre commented Mar 26, 2021

decebal commented Sep 9, 2021

studnik18 commented Sep 10, 2021

decebal commented Sep 10, 2021

jorisre commented Nov 5, 2020 •

edited

Loading

bluebill1049 commented Nov 16, 2020 •

edited

Loading

bluebill1049 commented Nov 17, 2020 •

edited

Loading

YimingIsCOLD commented Dec 23, 2020 •

edited

Loading

jorisre commented Jan 5, 2021 •

edited

Loading

MontoyaAndres commented Jan 24, 2021 •

edited

Loading

jorisre commented Jan 27, 2021 •

edited

Loading

borivojevic commented Jan 30, 2021 •

edited

Loading

jorisre commented Feb 1, 2021 •

edited

Loading

jorisre commented Feb 1, 2021 •

edited

Loading

hawkcookie commented Mar 2, 2021 •

edited

Loading