So for anyone still hitting this, ESM configuration explained in this section of documentation : https://kulshekhar.github.io/ts-jest/docs/guides/esm-support { // […] “jest”: { “extensionsToTreatAsEsm”: [“.ts”], “globals”: { “ts-jest”: { “useESM”: true } } } }
From your example: Case A: //utils.js export function doSomething() { //… } Case B: //utils.js export function doSomething() { //… } export default function doSomethingDefault() { //… } Result: import utils from ‘utils’ utils() // (Case A: undefined, Case B: doSomethingDefault) import * as utils from ‘utils’ utils // (Case A: utils = { doSomething: … Read more
You have to re-import or re-require your module. Check the doc or this issue for more information: https://github.com/facebook/jest/issues/3236 https://facebook.github.io/jest/docs/en/jest-object.html#jestresetmodules describe(‘MyModule’, () => { beforeEach(() => { jest.resetModules() }); describe(‘init’, () => { const myModule = require(‘./MyModule’); it(‘not throws exception when called’, () => { expect(() => myModule.init()).not.toThrow(); }); }) describe(‘do’, () => { const myModule … Read more
The simplest solution for this is adding jest: true to your env configuration in ESLint, like so: “env”: { “browser”: true, “node”: true, “jasmine”: true, “jest”: true, “es6”: true },
After doing some more research, I’ve found: Imports ARE hoisted! according to the spec of ModuleDeclarationInstantiation ALL the dependent Modules will be loaded before running any code. This code will have no errors, and will work: localFunc(); import {myFunc1} from ‘mymodule’; function localFunc() { // localFunc is hoisted myFunc1(); }
If you are not the library author and are having a problem consuming another library, you may be seeing an error like this: TypeError: [LIBRARY_NAME]__WEBPACK_IMPORTED_MODULE_3__ is not a constructor If that’s the case, you may be importing the library incorrectly in your code (it may be a problem with default exports). Double check the library … Read more
TLDR – Changing bable.config.<extension> to bable.config.cjs did the work. Check bable docs if you need a different config. SOLVED: For anyone who encounters this problem. This has got to do with Babel settings. The use of .mjs, cjs or js extension for the babel.config.extension. In my case where I was running LTE Node 12.6.2. I … Read more
You can use dynamic import within Chrome’s console. import(‘path/to/module.js’).then(m => module = m) // [doSomething] is an exported function from [module.js]. module.doSomething()
Module creates a scope to avoid name collisions. Either expose your function to window object import {hello} from ‘./test.js’ window.hello = hello Or use addEventListener to bind handler. Demo <button type=”button” id=”hello”>Click Me</button> <script type=”module”> import {hello} from ‘./test.js’ document.querySelector(‘#hello’).addEventListener(‘click’, hello) </script>
As long as import.meta.resolve stays experimental, you can use createRequire to get back the require.resolve functionality in ES modules, e.g. import { createRequire } from ‘node:module’; const require = createRequire(import.meta.url); const pathName = require.resolve(‘vue.runtime.esm.js’);