Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

hayleybech's avatar

Updating to Inertia 1.0 throws "Cannot use import statement outside a module"

When updating Inertia to 1.0, I get the following error when running my test suite:

Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /home/hayley/code/choirconcierge-main/node_modules/@inertiajs/core/node_modules/axios/index.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import axios from './lib/axios.js';
                                                                                      ^^^^^^

    SyntaxError: Cannot use import statement outside a module

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
      at Object.<anonymous> (node_modules/@inertiajs/core/src/debounce.ts:5:17)

I'm running Laravel Mix v6.0.43, here is my webpack.mix.js file:

const mix = require('laravel-mix');

/*
 |--------------------------------------------------------------------------
 | Mix Asset Management
 |--------------------------------------------------------------------------
 |
 | Mix provides a clean, fluent API for defining some Webpack build steps
 | for your Laravel application. By default, we are compiling the Sass
 | file for the application as well as bundling up all the JS files.
 |
 */
mix.js('resources/assets/js/app.js', 'public/js/app.js')
	.postCss('resources/assets/app.css', 'public/css/app.css', [
		require('tailwindcss')
	])
	.extract()
	.react()
	.ts('resources/assets/js/test.ts', 'public/js');

const path = require('path');
mix.alias({
	ziggy: path.resolve('vendor/tightenco/ziggy/dist'),
});

mix.version();

I'm really lost on this one, I'd really appreciate any direction, I'm not even sure where to start.

0 likes
2 replies
hayleybech's avatar

9 months later, I finally got around to looking at it again, and worked it out! I was able to avoid the issue by mocking Inertia / inertia's Link component. There may be another solution, but that's good enough for me!

gych's avatar

In your package.json file try to set type to module

"type": "module",

Please or to participate in this conversation.