CODEWITHSUNDEEP
javascriptnode.jsnode-modulespackage.jsonnpm-package
Nick
Nick

Reputation: 6362

SyntaxError: Cannot use import statement outside a module (from dependency)

How do you resolve "Cannot use import statement outside a module" from a dependency when the dependency isn't declared as a module?

I want to use the validator in Svelte/kit to validate emails. However, when importing the ESM version, I get the "Cannot use import statement outside a module" error. I'm using pnpm instead of npm or yarn.

import isEmail from 'validator/es/lib/isEmail'

/node_modules/.pnpm/[email protected]/node_modules/validator/es/lib/isEmail.js:1
import assertString from './util/assertString';
^^^^^^

SyntaxError: Cannot use import statement outside a module
    at Object.compileFunction (node:vm:355:18)
    at wrapSafe (node:internal/modules/cjs/loader:1039:15)
    at Module._compile (node:internal/modules/cjs/loader:1073:27)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1138:10)
    at Module.load (node:internal/modules/cjs/loader:989:32)
    at Function.Module._load (node:internal/modules/cjs/loader:829:14)
    at Module.require (node:internal/modules/cjs/loader:1013:19)
    at require (node:internal/modules/cjs/helpers:93:18)
    at nodeRequire

It appears that validator is attempting to use the import statement, but it's package.json does not specify "type": "module". My guess is that this is the root cause of the error.

Debug steps

Related

Metadata

Upvotes: 13

Views: 10931

Answers (6)

GRASBOCK
GRASBOCK

Reputation: 737

For those that happen to have the same problem while deploying with nodejs using typescript.

"type":"module" was already set in my package.json in the main project. I put the build directory on the server (created by npm run build).

working-dir
  |--build
       |--index.js
       |--...

I thought i had to just run node build/index.js, as I thought everything was packaged. Turns out I need to add a package.json into the working directory (I think it also works by putting it into the build directory).

server
+ |--package.json 
  |--build
       |--index.js
       |--...

// package.json
{
  "type": "module"
}

Upvotes: 1

AngelNext
AngelNext

Reputation: 158

Try importing like this

import { isEmail } from "validator"

Upvotes: 0

Anthony
Anthony

Reputation: 979

After reading their docs: https://github.com/validatorjs/validator.js#es6, it looks like the es part in the import is, so it can be treeshakable. You can fix this error, by just importing it normally:

import isURL from 'validator/lib/isURL';

Upvotes: 0

Leftium
Leftium

Reputation: 17903

Have you tried importing like this?

import validator from 'validator'

I tried reproducing your issue with latest SvelteKit. This works fine:

// index.svelte
<script>
    import validator from 'validator';
    let result = validator.isEmail('[email protected]');
    console.log(result);
</script>

When I changed the import statement to:

import validator from 'validator/es/lib/isEmail'

I got the error from your question (Cannot use import statement outside a module).

Importing validator/es/lib/isEmail supposedly only imports a subset of the library. I'm not sure how much difference it will make; it might not make any difference. A slightly larger build beats a build that doesn't work. I suggest getting it working first, then optimize the build size if you really need to.

Upvotes: 5

Saiful Islam
Saiful Islam

Reputation: 23

Try to import like below

const {isEmail} = require('validator');

Upvotes: -2

mik rus
mik rus

Reputation: 139

Without more information, if your problem solely lies in a problem with code you are dependent on, consider short term using something like patch-package to make the necessary adjustment, and long term, open up a PR over at the validator.js repo!

for patch-package, just go add the "type": "module" to the package.json at node_modules/validator, and then run npx patch-package validator. You can then version control the outputted diff file, and the changes are made automatically with npm hooks assuming patch-package is a (dev) dependency.

The behavior or defect of the library here is probably from the devs more keeping in mind things like webpack that do esm imports on their own terms, and not with the node module resolution patterns that it appears svelte is using. or at least how the problem has gotten this far.(might be wrong about this!).

Upvotes: 0

Related Questions