[Bug]: verbatimModuleSyntax support #4081

simPod · 2023-04-03T10:35:25Z

Version

v29.1.0

Steps to reproduce

I have upgraded to TS v5. I had to replace importsNotUsedAsValues: 'error' with verbatimModuleSyntax: true

Expected behavior

No error.

Actual behavior

ESM syntax is not allowed in a CommonJS module when 'verbatimModuleSyntax' is enabled.

for import { xxx } from './xxx';

Debug log

https://gist.github.com/simPod/90d2228089b7a8b1b16a827f73aa71f2

Additional context

config

module.exports = {
  preset: 'ts-jest',
};

Environment

System:
    OS: macOS 13.2.1
    CPU: (10) arm64 Apple M1 Max
  Binaries:
    Node: 19.6.1 - /opt/homebrew/bin/node
    Yarn: 4.0.0-rc.42 - /opt/homebrew/bin/yarn
    npm: 9.4.0 - /opt/homebrew/bin/npm

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

ahnpnl · 2023-04-03T10:38:25Z

The error says that option only works with ESM mode while you are using commonjs mode. You can check documentation how to enable ESM mode. Thanks.

simPod · 2023-04-03T10:46:36Z

Thanks for reply. I have never seen the docs since I've used jest without esm mode until now with no issues.

However, I've followed the docs. And getting the same error even wit modified config:

/** @type {import('ts-jest').JestConfigWithTsJest} */
module.exports = {
  moduleNameMapper: {
    '^(\\.{1,2}/.*)\\.js$': '$1',
  },
  preset: 'ts-jest/presets/default-esm',
  transform: {
    '^.+\\.tsx?$': [
      'ts-jest',
      { useESM: true },
    ],
  },
};

ahnpnl · 2023-04-03T10:53:30Z

Sorry the doc was a bit outdated, there is warning about using transform and preset see https://kulshekhar.github.io/ts-jest/docs/getting-started/options

the doc for ESM needs to be updated accordingly.

the error you saw came from TS type checking similar to tsc which we can’t control which options require ESM.

you should follow the manual configuration under ESM support doc which gives more control

simPod · 2023-04-03T10:58:57Z

I have inspected default-esm preset which basically just sets extensionsToTreatAsEsm: ['.ts', '.tsx', '.mts'].
Not sure whether I'm missing something in your reply about we can’t control which options require ESM but I see the same error still.

/** @type {import('ts-jest').JestConfigWithTsJest} */
module.exports = {
  extensionsToTreatAsEsm: ['.ts', '.tsx', '.mts'],
  moduleNameMapper: {
    '^(\\.{1,2}/.*)\\.js$': '$1',
  },
  transform: {
    '^.+\\.tsx?$': [
      'ts-jest',
      { useESM: true },
    ],
  },
};

tsconfig has "module": "ESNext",

ahnpnl · 2023-04-03T11:01:17Z

Would you please put a reproduce example with this https://github.com/kulshekhar/ts-jest/tree/main/examples/ts-only

simPod · 2023-04-03T11:01:46Z

on it

simPod · 2023-04-03T11:16:39Z

#4082

juanjoDiaz · 2023-04-08T16:50:46Z

Hi @ahnpnl ,

I'm still facing this issue.

I've tried the default preset:

{
  preset: 'ts-jest/presets/default-esm', // or other ESM presets
  moduleNameMapper: { '^(\\.{1,2}/.*)\\.js$': '$1' },
  testEnvironment: 'node',
  testMatch: ['<rootDir>/**/test/*.ts', '<rootDir>/**/test/types/*.ts'],
  collectCoverageFrom: ['src/**'],
}

and the manual config:

{
  extensionsToTreatAsEsm: ['.ts', '.tsx', '.mts'],
  transform: {
    '^.+\\.tsx?$': [
      'ts-jest',
      { useESM: true, isolatedModules: false },
    ],
  },
  moduleNameMapper: { '^(\\.{1,2}/.*)\\.js$': '$1' },
  testEnvironment: 'node',
  testMatch: ['<rootDir>/**/test/*.ts', '<rootDir>/**/test/types/*.ts'],
  collectCoverageFrom: ['src/**'],
}

However, none of them worked.
I keep getting jest.config.ts:12:1 - error TS1286: ESM syntax is not allowed in a CommonJS module when 'verbatimModuleSyntax' is enabled.

Any suggestion?

ahnpnl · 2023-04-09T12:31:22Z

@juanjoDiaz You can use this PR example to try out #4083 note that, this new tsconfig option only works with ESM mode so you need to choose the correct jest config file in one of those examples

juanjoDiaz · 2023-04-09T16:37:52Z

Hi @ahnpnl ,

Thanks for the quick response.

I tried

import preset from 'ts-jest/presets/index.js'

/** @type {import('ts-jest').JestConfigWithTsJest} */
export default {
  ...preset.defaultsESM,
  transform: {
    '^.+\\.tsx?$': [
      'ts-jest',
      {
        useESM: true,
      },
    ],
  },
}

as per the PR but I'm getting the same error.

Can you be a bit more specific on where the issue is and what setting in the config would allow me to treat the "jest.config.ts" as an esm module?

ahnpnl · 2023-04-09T17:38:33Z

jest.config.ts is not handled by ts-jest but Jest itself does.

juanjoDiaz · 2023-04-10T09:20:01Z

But Jest is a js-only solution, right?

If my jest config is a TS file, it must be parsed by ts-node isn't it?
That's where the issue seems to be.

ahnpnl · 2023-04-10T10:03:37Z

Jest handles loading config while ts-jest handles transforming test files, source files which are used by test files. Indeed Jest uses ts-node to parse your config file.

juanjoDiaz · 2023-04-10T16:52:41Z

Indeed.
So, the issue that I am seeing when parsing the jest config file using the verbatimModuleSyntax option is related to ts-node.
Isn't that related to ts-jest?
Or does jest include its own ts-node to parse config files?

ahnpnl · 2023-04-10T17:02:28Z

ts-jest only executes after Jest finishes processing tsconfig. Jest requires you to install ts-node to process Jest ts config. ts-jest doesn’t interfere with how Jest processes config file.

dustin-ruetz · 2023-04-11T16:06:02Z

I haven't been able to figure out the root cause of this issue, but after reviewing the /examples/ts-only folder I found that the config in jest-esm-isolated.config.mjs resolves the error for my projects. More specifically, setting isolatedModules to true in the ts-jest transfom config object is what fixed the issue for me.

Below is a summary of the changes that I made to get ts-jest working with TypeScript 5; hopefully this will help some folks who come across this issue in the future.

// ./package.json
// (trimmed to just the relevant parts)
"devDependencies": {
	"@types/jest": "^29.5.0",
	"jest": "^29.5.0",
	"ts-jest": "^29.1.0",
	"typescript": "^5.0.4"
}

// ./tsconfig.json
// (trimmed to just the relevant parts)
 		"esModuleInterop": true,
-		"importsNotUsedAsValues": "error",
-		"isolatedModules": true,
 		"module": "esnext",
 		"moduleResolution": "node",
 		"strict": true,
 		"target": "es2022",
+		"verbatimModuleSyntax": true
 	}
 }

// ./config/jest.config.js
// (trimmed to just the relevant parts)
 	transform: {
-		".ts": ["ts-jest"],
+		".ts": [
+			"ts-jest",
+			{
+				// Note: We shouldn't need to include `isolatedModules` here because it's a deprecated config option in TS 5,
+				// but setting it to `true` fixes the `ESM syntax is not allowed in a CommonJS module when
+				// 'verbatimModuleSyntax' is enabled` error that we're seeing when running our Jest tests.
+				isolatedModules: true,
+				useESM: true,
+			},
+		],
 	},

juanjoDiaz · 2023-04-11T16:57:44Z

That solution doesn't work for me 🙁

I get the error when parsing the actual jest.config.ts file. So the solution has to be somewhere else.

mengxinssfd · 2023-04-20T06:00:28Z

I haven't been able to figure out the root cause of this issue, but after reviewing the /examples/ts-only folder I found that the config in jest-esm-isolated.config.mjs resolves the error for my projects. More specifically, setting isolatedModules to true in the ts-jest transfom config object is what fixed the issue for me.

Below is a summary of the changes that I made to get ts-jest working with TypeScript 5; hopefully this will help some folks who come across this issue in the future.

// ./package.json
// (trimmed to just the relevant parts)
"devDependencies": {
	"@types/jest": "^29.5.0",
	"jest": "^29.5.0",
	"ts-jest": "^29.1.0",
	"typescript": "^5.0.4"
}

// ./tsconfig.json
// (trimmed to just the relevant parts)
 		"esModuleInterop": true,
-		"importsNotUsedAsValues": "error",
-		"isolatedModules": true,
 		"module": "esnext",
 		"moduleResolution": "node",
 		"strict": true,
 		"target": "es2022",
+		"verbatimModuleSyntax": true
 	}
 }

// ./config/jest.config.js
// (trimmed to just the relevant parts)
 	transform: {
-		".ts": ["ts-jest"],
+		".ts": [
+			"ts-jest",
+			{
+				// Note: We shouldn't need to include `isolatedModules` here because it's a deprecated config option in TS 5,
+				// but setting it to `true` fixes the `ESM syntax is not allowed in a CommonJS module when
+				// 'verbatimModuleSyntax' is enabled` error that we're seeing when running our Jest tests.
+				isolatedModules: true,
+				useESM: true,
+			},
+		],
 	},

@dustin-ruetz Thanks, this answer is useful.
But it seems to conflict with "moduleResolution": "bundler" of tsconfig, and it will be invalid after adding.
In order to solve this error, I configured a tsconfig specifically for jest, fortunately it is useful.

// jest.config.js
transform: {
+    '.ts': ['ts-jest', { tsconfig: './tsconfig.jest.json' }],
},

tsconfig.jest.json

{
  "extends": "./tsconfig.json",
  "compilerOptions": {
    "verbatimModuleSyntax": false
  }
}

skjnldsv · 2023-06-27T14:20:14Z

If you use a jest.config.ts file name, you also need to fix the main tsconfig :/

diff --git a/__tests__/tsconfig.json b/__tests__/tsconfig.json
--- /dev/null
+++ b/__tests__/tsconfig.json
@@ -0,0 +1,6 @@
+{
+	"extends": "../tsconfig.json",
+	"compilerOptions": {
+		"verbatimModuleSyntax": false
+	}
+}

diff --git a/jest.config.ts b/jest.config.ts
--- a/jest.config.ts
+++ b/jest.config.ts
@@ -55,6 +55,10 @@ const config: Config = {
 		// process `*.js` files with `babel-jest`
 		'^.+\\.js$': 'babel-jest',
 		'^.+\\.vue$': '@vue/vue2-jest',
+		'^.+\\.ts$': ['ts-jest', {
+			// @see https://github.com/kulshekhar/ts-jest/issues/4081
+			tsconfig: './__tests__/tsconfig.json',
+		}],
 	},
 	transformIgnorePatterns: [
 		'node_modules/(?!(' + ignorePatterns.join('|') + ')/)',

diff --git a/tsconfig.json b/tsconfig.json
--- a/tsconfig.json
+++ b/tsconfig.json
@@ -19,7 +19,8 @@
 		// these options are overrides used only by ts-node
 		// same as our --compilerOptions flag and our TS_NODE_COMPILER_OPTIONS environment variable
 		"compilerOptions": {
-			"module": "commonjs"
+			"module": "commonjs",
+			"verbatimModuleSyntax": false
 		}
 	}
 }

As described in kulshekhar/ts-jest#4081 (comment).

seanblonien · 2023-12-01T00:52:33Z

That solution doesn't work for me 🙁

I get the error when parsing the actual jest.config.ts file. So the solution has to be somewhere else.

yup - same here. the issue always happened when resolving any ESM jest config file (including ts config files), it gave the original error: ESM syntax is not allowed in a CommonJS module when 'verbatimModuleSyntax' is enabled.

seems like the issue has to do with parsing the config file in ESM, but typescript is used (I believe) to do so, but TypeScript keeps complaining about "verbatimModuleSyntax" even when you specify a custom tsconfig config or config file in the "transform" key... soo the trick is to just disable the "verbatimModuleSyntax" TS config, BUT you can't use the new transform key, because that is exactly what is breaking, and so you have to use the now deprecated "globals" key instead, and it just worked for me:

// jest.config.cjs
/** @type {import('ts-jest').JestConfigWithTsJest} */
module.exports = {
+   globals: {
+     'ts-jest': {
+       useESM: true,
+       tsconfig: {
+         verbatimModuleSyntax: false,
+       },
+     },
+   },
- transform: {
-    '.ts': ['ts-jest', { tsconfig: './tsconfig.jest.json' }],
- },
  preset: 'ts-jest/presets/default-esm',
  testEnvironment: 'node',
};

when i run jest cli, I do get this annoying warning, but tests are running

> jest

ts-jest[ts-jest-transformer] (WARN) Define `ts-jest` config under `globals` is deprecated. Please do
transform: {
    <transform_regex>: ['ts-jest', { /* ts-jest config goes here in Jest */ }],
},
 PASS  test/test1.spec.ts
...

this method very simply disables the "verbatimModuleSyntax" tsconfig value to false when TS is used as a transformer in my tests files, but the normal tsconfig.json still works for the test files in my editor

it seems to me likely that ts-jest is the culprit here as there is strictly different behaviour happening with the globals and the transform keys. pretty clear ts-jest doesn't support "verbatimModuleSyntax" whatsoever in the like 12 permutations of settings i tried with ESM jest config file. i really did try eveyrthing in this thread and had to give up on "everything" being TS/ESM. is it so hard to use TS for everything and use jest? apparently yes it is haha

don't exactly have time to create a new issue from this, but is very reproducible if you just switch the place of the tsconfig object/path from transform to globals if anyone else wants to create a new issue for this ongoing bug

KrisSimon · 2024-02-07T08:02:34Z

The solution from @seanblonien does not work for me as well. (It's February 2024). I decided to bury Jest and go with Vitest. In my Svelte project that works out of the box. The question remains as to how long this system will work.

randre70 · 2024-02-21T17:51:23Z

If I have package.json containing "type": "module", node is complaining if .js is missing. Therefore tsconfig.jest.json has to have "verbatimModuleSyntax": true.
I have no cue how to fix this. Why is this issue closed?

randre70 · 2024-02-21T17:52:32Z

That solution doesn't work for me 🙁
I get the error when parsing the actual jest.config.ts file. So the solution has to be somewhere else.

yup - same here. the issue always happened when resolving any ESM jest config file (including ts config files), it gave the original error: ESM syntax is not allowed in a CommonJS module when 'verbatimModuleSyntax' is enabled.

seems like the issue has to do with parsing the config file in ESM, but typescript is used (I believe) to do so, but TypeScript keeps complaining about "verbatimModuleSyntax" even when you specify a custom tsconfig config or config file in the "transform" key... soo the trick is to just disable the "verbatimModuleSyntax" TS config, BUT you can't use the new transform key, because that is exactly what is breaking, and so you have to use the now deprecated "globals" key instead, and it just worked for me:
// jest.config.cjs
/** @type {import('ts-jest').JestConfigWithTsJest} */
module.exports = {
+   globals: {
+     'ts-jest': {
+       useESM: true,
+       tsconfig: {
+         verbatimModuleSyntax: false,
+       },
+     },
+   },
- transform: {
-    '.ts': ['ts-jest', { tsconfig: './tsconfig.jest.json' }],
- },
  preset: 'ts-jest/presets/default-esm',
  testEnvironment: 'node',
};
when i run jest cli, I do get this annoying warning, but tests are running
> jest

ts-jest[ts-jest-transformer] (WARN) Define `ts-jest` config under `globals` is deprecated. Please do
transform: {
    <transform_regex>: ['ts-jest', { /* ts-jest config goes here in Jest */ }],
},
 PASS  test/test1.spec.ts
...
this method very simply disables the "verbatimModuleSyntax" tsconfig value to false when TS is used as a transformer in my tests files, but the normal tsconfig.json still works for the test files in my editor

it seems to me likely that ts-jest is the culprit here as there is strictly different behaviour happening with the globals and the transform keys. pretty clear ts-jest doesn't support "verbatimModuleSyntax" whatsoever in the like 12 permutations of settings i tried with ESM jest config file. i really did try eveyrthing in this thread and had to give up on "everything" being TS/ESM. is it so hard to use TS for everything and use jest? apparently yes it is haha

don't exactly have time to create a new issue from this, but is very reproducible if you just switch the place of the tsconfig object/path from transform to globals if anyone else wants to create a new issue for this ongoing bug

Can you point at an example repository where this is working?

airtonix · 2024-03-18T22:03:24Z

Just commenting here in case most of you are using verbatimModuleSyntax as a linting mechansim so that your eslint auto fixes your imports to type only imports.

https://johnnyreilly.com/typescript-5-importsnotusedasvalues-error-eslint-consistent-type-imports

If you are, then it appears that you only need:

      "rules": {
        "@typescript-eslint/consistent-type-imports": "error"
      }

and if you're using vscode, then also this in .vscode/settings.json or your *.code-workspace.json#settings

    "editor.formatOnSave": true,
    "editor.codeActionsOnSave": {
      "source.fixAll.eslint": "always", // or explicit
      "source.fixAll": "always",  // or explicit
    },

    "eslint.enable": true,
    "eslint.format.enable": true,

You can can avoid all these errors by not using that option, but still get the eslint behaviour.

Yes i just suggested fixing the problem by turning the errors off. 😅

kulshekhar/ts-jest#4081 (comment) https://koenvg.medium.com/setting-up-jest-with-sveltekit-4f0a0e379668#3f2e https://github.com/pmucha/sveltekit-jest-setup

- Because of error "ESM syntax is not allowed in a CommonJS module when 'verbatimModuleSyntax' is enabled." when running tests. - The GitHub issue also suggested to just use the eslint version: kulshekhar/ts-jest#4081

davidandreoletti · 2024-07-01T07:24:05Z

jest.config.ts is not handled by ts-jest but Jest itself does.

More precisely transpiled by 'ts-node'.

theycallmeswift · 2024-08-08T00:34:13Z

This is still an issue in Aug 2024 FYI. Specifically ts-jest does not properly parse jest.config.ts files when "verbatimModuleSyntax": true,

ahnpnl · 2024-08-08T13:34:47Z

ESM syntax is not allowed in a CommonJS module when 'verbatimModuleSyntax' is enabled.

ts-jest doesn't handle parsing of jest.config.ts. ts-jest only transpiles codes which are given by jest-runtime. jest-runtime takes care of reading jest.config.ts

lvlte · 2024-08-25T12:07:15Z

Why is this issue closed as "completed" ?

Suppose you have an ESM module (package.json contains "type": "module") with the following in tsconfig (no path options) :

    "module": "nodenext",
    "moduleResolution": "nodenext",
    "verbatimModuleSyntax": true,
    "esModuleInterop": true

Your jest config (defined in jest.config.js, ie. ts-node not involved), as recommended by the doc (except for the CJS syntax obviously, and without the unnecessary / redundant settings that are already [pre]set) :

export default {
  preset: 'ts-jest/presets/default-esm'
};

You run your tests and get the error : "ESM syntax is not allowed in a CommonJS module when 'verbatimModuleSyntax' is enabled" 😮.

Adding isolatedModules: true - thanks @dustin-ruetz - makes the error go away :

export default {
  preset: 'ts-jest/presets/default-esm',
  transform: {
    '.ts': [
      'ts-jest',
      {
        isolatedModules: true
      }
    ]
  }
};

😮

Would it not be a bug ?

We shouldn't have to set isolatedModules: true or verbatimModuleSyntax: false to get rid of an error that says our ESM module is a CJS module.

This is not a feature request.

ahnpnl · 2024-08-25T12:19:21Z

The original report is about jest config in typescript doesn’t work with this option. We closed this issue because ts-jest doesn’t handle that.

However, your issue is a different one which is related to #4198

lvlte · 2024-08-25T12:58:36Z

We closed this issue because ts-jest doesn’t handle that.

Ok, great.

So why the error doesn't reflect that with a clear message : ts-jest doesn’t handle "verbatimModuleSyntax" ?
Rather than ESM syntax is not allowed in a CommonJS module when "verbatimModuleSyntax" is enabled ?

However, your issue is a different one which is related to #4198

How is it related ?

verbatimModuleSyntax is not mentioned at all in the issue description nor in the comments.
people say they only encounter the issue with isolatedModules: true, the exact opposite of what people say here.

ahnpnl · 2024-08-25T13:12:28Z

I think there are 2 things in this issue: one is about Jest config in typescript doesn't work with verbatimModuleSyntax and one is about transforming issue. At some point, I thought the original issue was about working with jest.config.ts so I closed this issue.

If you have issues with your jest.config.ts, ts-jest can't solve it unfortunately.

If you have transforming issue, for example your other ts files, would you pls provide an example in any of the projects here https://github.com/kulshekhar/ts-jest/tree/main/examples. Based on your input, we can repopen this issue and fix it properly.

lvlte · 2024-08-25T13:18:09Z

All you need to reproduce the issue is in my first comment. The content of my .ts files is not relevant.

Just take an esm package with the config I mentioned and an index.ts file that exports something, then try to import it in a test file and see the results.

Note I use jest.config.js (not .ts).

simPod added Bug Report Needs Triage labels Apr 3, 2023

ahnpnl closed this as completed Apr 3, 2023

ahnpnl added Not An Issue Not ts-jest issue and removed Bug Report Needs Triage labels Apr 3, 2023

simPod mentioned this issue Apr 3, 2023

verbatimModuleSyntax support #4082

Closed

evantill mentioned this issue Apr 9, 2023

[Bug]: verbatimModuleSyntax support jestjs/jest#14047

Closed

dustin-ruetz mentioned this issue Apr 13, 2023

Migrate action to Typescript 1Password/load-secrets-action#36

Merged

kachick mentioned this issue Apr 17, 2023

Welcome TypeScript 5 era kachick/action-typescript-template#287

Closed

claremacrae mentioned this issue Jul 11, 2023

build(deps-dev): bump @tsconfig/svelte from 3.0.0 to 5.0.0 obsidian-tasks-group/obsidian-tasks#2077

Closed

Aleksbgbg added a commit to Aleksbgbg/streamfox that referenced this issue Jul 15, 2023

Add specific tsconfig for jest to fix TypeScript support issue.

a924ada

As described in kulshekhar/ts-jest#4081 (comment).

MaddyGuthridge added a commit to MaddyGuthridge/Minifolio that referenced this issue May 19, 2024

Get Jest working

7c6584b

kulshekhar/ts-jest#4081 (comment) https://koenvg.medium.com/setting-up-jest-with-sveltekit-4f0a0e379668#3f2e https://github.com/pmucha/sveltekit-jest-setup

ahnpnl reopened this Aug 8, 2024

ahnpnl added 🚀 Feature Request new suggested feature and removed Not An Issue Not ts-jest issue labels Aug 8, 2024

ahnpnl closed this as completed Aug 8, 2024

freemvmt mentioned this issue Aug 16, 2024

[api] implement verbatim module syntax in tsconfig theopensystemslab/planx-new#3528

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Bug]: verbatimModuleSyntax support #4081

[Bug]: verbatimModuleSyntax support #4081

simPod commented Apr 3, 2023

ahnpnl commented Apr 3, 2023

simPod commented Apr 3, 2023 •

edited

Loading

ahnpnl commented Apr 3, 2023 •

edited

Loading

simPod commented Apr 3, 2023 •

edited

Loading

ahnpnl commented Apr 3, 2023

simPod commented Apr 3, 2023

simPod commented Apr 3, 2023

juanjoDiaz commented Apr 8, 2023

ahnpnl commented Apr 9, 2023 •

edited

Loading

juanjoDiaz commented Apr 9, 2023

ahnpnl commented Apr 9, 2023

juanjoDiaz commented Apr 10, 2023

ahnpnl commented Apr 10, 2023

juanjoDiaz commented Apr 10, 2023

ahnpnl commented Apr 10, 2023 •

edited

Loading

dustin-ruetz commented Apr 11, 2023 •

edited

Loading

juanjoDiaz commented Apr 11, 2023

mengxinssfd commented Apr 20, 2023 •

edited

Loading

skjnldsv commented Jun 27, 2023

seanblonien commented Dec 1, 2023

KrisSimon commented Feb 7, 2024

randre70 commented Feb 21, 2024

randre70 commented Feb 21, 2024

airtonix commented Mar 18, 2024 •

edited

Loading

davidandreoletti commented Jul 1, 2024

theycallmeswift commented Aug 8, 2024

ahnpnl commented Aug 8, 2024

lvlte commented Aug 25, 2024

ahnpnl commented Aug 25, 2024

lvlte commented Aug 25, 2024

ahnpnl commented Aug 25, 2024 •

edited

Loading

lvlte commented Aug 25, 2024 •

edited

Loading

[Bug]: verbatimModuleSyntax support #4081

[Bug]: verbatimModuleSyntax support #4081

Comments

simPod commented Apr 3, 2023

Version

Steps to reproduce

Expected behavior

Actual behavior

Debug log

Additional context

Environment

ahnpnl commented Apr 3, 2023

simPod commented Apr 3, 2023 • edited Loading

ahnpnl commented Apr 3, 2023 • edited Loading

simPod commented Apr 3, 2023 • edited Loading

ahnpnl commented Apr 3, 2023

simPod commented Apr 3, 2023

simPod commented Apr 3, 2023

juanjoDiaz commented Apr 8, 2023

ahnpnl commented Apr 9, 2023 • edited Loading

juanjoDiaz commented Apr 9, 2023

ahnpnl commented Apr 9, 2023

juanjoDiaz commented Apr 10, 2023

ahnpnl commented Apr 10, 2023

juanjoDiaz commented Apr 10, 2023

ahnpnl commented Apr 10, 2023 • edited Loading

dustin-ruetz commented Apr 11, 2023 • edited Loading

juanjoDiaz commented Apr 11, 2023

mengxinssfd commented Apr 20, 2023 • edited Loading

skjnldsv commented Jun 27, 2023

seanblonien commented Dec 1, 2023

KrisSimon commented Feb 7, 2024

randre70 commented Feb 21, 2024

randre70 commented Feb 21, 2024

airtonix commented Mar 18, 2024 • edited Loading

davidandreoletti commented Jul 1, 2024

theycallmeswift commented Aug 8, 2024

ahnpnl commented Aug 8, 2024

lvlte commented Aug 25, 2024

ahnpnl commented Aug 25, 2024

lvlte commented Aug 25, 2024

ahnpnl commented Aug 25, 2024 • edited Loading

lvlte commented Aug 25, 2024 • edited Loading

simPod commented Apr 3, 2023 •

edited

Loading

ahnpnl commented Apr 3, 2023 •

edited

Loading

simPod commented Apr 3, 2023 •

edited

Loading

ahnpnl commented Apr 9, 2023 •

edited

Loading

ahnpnl commented Apr 10, 2023 •

edited

Loading

dustin-ruetz commented Apr 11, 2023 •

edited

Loading

mengxinssfd commented Apr 20, 2023 •

edited

Loading

airtonix commented Mar 18, 2024 •

edited

Loading

ahnpnl commented Aug 25, 2024 •

edited

Loading

lvlte commented Aug 25, 2024 •

edited

Loading