Skip to content Skip to footer

Tackling the “Cannot Use Import Statement Outside a Module” Error in JavaScript

Ah, the classic JavaScript hiccup: “Cannot use import statement outside a module.” It’s like a rite of passage for developers diving into the modern JavaScript ecosystem. But fear not, my fellow code wranglers! We’re about to dissect this error and show you how to fix it across different JavaScript environments, because let’s face it, we’ve all been there at 2 AM, Googling furiously for a solution while our coffee goes cold.

What’s the Deal with ES Modules?

First, let’s get our heads around ES Modules (ESM). They’re the official standard format to package JavaScript code for reuse. With ESM, you can create tidy, maintainable modules and import them into other files with a sweet, sweet import statement. But here’s the kicker: if your environment isn’t set up to handle ESM, JavaScript will throw a tantrum in the form of the “Cannot use import statement outside a module” error.

Setting Up Your Project to Use ES Modules

To get the ball rolling with ES Modules, you need to give JavaScript a heads up. For Node.js projects, you’ll want to add a little nugget in your package.json:

  "type": "module"

This tells Node.js, “Hey, we’re playing with ES Modules here!” Without this, Node.js assumes you’re using CommonJS modules, which is an older format.

Dealing with the Error in Node.js

Imagine you’ve got a file, coolModule.js, that exports a function:

// coolModule.js
export function doTheCoolThing() {
  console.log("Doing the cool thing!");

And you’re trying to import it in app.js:

// app.js
import { doTheCoolThing } from './coolModule.js';


If Node.js isn’t set up for ESM, it’ll hit you with the dreaded error. But if you’ve added the "type": "module" in your package.json, you’re golden.

When Browsers Complain

Browsers are a bit different. They need to know which <script> tags contain modules. So, you’ll tag them with type="module", like this:

<!-- index.html -->
<script type="module" src="app.js"></script>

This signals to the browser that app.js is a module, and it should treat it as such.

Framework-Specific Fixes

Alright, let’s talk about some popular frameworks and how they handle modules.

React with Create React App

If you’re using Create React App, you’re in luck. It’s set up for ES Modules out of the box. Just start importing and exporting to your heart’s content.

Here’s a quick example:

// FancyComponent.js
import React from 'react';

export default function FancyComponent() {
  return <div>I'm so fancy!</div>;

Vue with Vue CLI

Vue developers, you’re also covered. Vue CLI projects support ES Modules right from the get-go.

// MyVueComponent.vue
  <p>{{ message }}</p>

export default {
  data() {
    return {
      message: 'Vue is pretty cool!'

Angular with Angular CLI

Angular? No sweat. Angular CLI has your back with built-in ES Module support.

// app.component.ts
import { Component } from '@angular/core';

  selector: 'app-root',
  template: `<h1>{{ title }}</h1>`
export class AppComponent {
  title = 'Angular is nifty!';


Svelte users, you too can breathe easy. Svelte supports ES Modules by default, making your development process smooth as butter.

<!-- App.svelte -->
  export let name;

<h1>Hello {name}!</h1>

Conclusion of the First Half

We’ve covered the basics of the “Cannot use import statement outside a module” error and how to fix it in Node.js and browsers. Plus, we’ve taken a quick tour of how some of the most popular frameworks handle ES Modules.

Stay tuned for the second half of this article, where we’ll dive into more advanced scenarios, including dynamic imports and how to work with third-party libraries that might not be as cooperative. We’ll also look at some best practices to keep your module game strong and error-free. Happy coding until then!

We’ve already tackled the basics of ES Modules and how to get past the initial hurdle in various environments. Now, let’s level up and explore some more advanced scenarios, including dynamic imports and dealing with third-party libraries that aren’t playing nice with your module setup.

Dynamic Imports in JavaScript

Sometimes, you need to load modules on the fly, maybe based on user actions or some other runtime condition. That’s where dynamic imports come in. They let you import modules dynamically and return a promise that resolves to the module.

Here’s an example:

// Assume we have a module named `dynamicModule.js` that exports a `surprise` function.
button.addEventListener('click', async () => {
  if (userNeedsSurprise) {
    const { surprise } = await import('./dynamicModule.js');

This way, dynamicModule.js is only loaded when it’s actually needed, which can significantly improve the performance of your application.

Handling Third-Party Libraries

What do you do when a third-party library isn’t exported as an ES Module? You might encounter libraries that are still using the CommonJS format. Thankfully, most bundlers, like Webpack and Rollup, provide ways to include these libraries in your module-based project.

For instance, with Webpack, you can configure it to handle CommonJS modules:

// webpack.config.js
module.exports = {
  // ...
  module: {
    rules: [
        test: /\.js$/,
        use: {
          loader: 'babel-loader',
          options: {
            presets: ['@babel/preset-env'],
            plugins: ['@babel/plugin-transform-modules-commonjs']
  // ...

This setup uses Babel to transform CommonJS modules into a format that Webpack can bundle alongside your ES Modules.

Best Practices for Working with ES Modules

When working with modules, it’s important to follow some best practices to avoid errors and keep your codebase maintainable:

  1. Use file extensions in import statements: Node.js and some browsers require the .js extension in import paths, so it’s a good habit to include them.

    // Do this
    import { myFunction } from './myModule.js';
    // Instead of this
    import { myFunction } from './myModule';
  2. Be explicit about imported bindings: Use named imports and exports where possible, as they make your code more readable and easier to refactor.

    // Do this
    import { specificFunction } from 'library';
    // Instead of this
    import * as Library from 'library';
  3. Keep an eye on the tree-shaking: When using bundlers, make sure they are configured for tree-shaking to eliminate dead code from your final bundle.

  4. Stay up to date with library versions: Libraries are constantly being updated to support ES Modules. Always check if a newer version of a library supports ESM before resorting to workarounds.

  5. Consider using a linter: Tools like ESLint can help catch errors and enforce best practices in your module usage.


We’ve now explored the depths of ES Modules, from setting up your environment to handling dynamic imports and integrating third-party libraries. By following the guidance provided and adhering to best practices, you’ll be able to harness the full power of ES Modules and keep your JavaScript projects clean, efficient, and modern.

Remember, the JavaScript ecosystem is always evolving, and with it, the module landscape will continue to change. Stay curious, keep experimenting, and don’t let the occasional error throw you off your game. Happy coding, and may your imports always be error-free!