import "mod" in api_esm.mjs leads to crash if bundling with webpack

Hi, I am bundling Chevrotain with Webpack in my Argdown language-server. This currently creates a lot of the following warnings:

WARNING in ../argdown-core/node_modules/chevrotain/lib_esm/api_esm.mjs 11:27-42
export 'default' (imported as 'mod') was not found in '../lib/src/api.js' (possible exports: Alternation, Alternative, CstParser, EMPTY_ALT, EOF, EarlyExitException, EmbeddedActionsParser, GAstVisitor, Lexer, LexerDefinitionErrorType, MismatchedTokenException, NoViableAltException, NonTerminal, NotAllInputParsedException, Option, Parser, ParserDefinitionErrorType, Repetition, RepetitionMandatory, RepetitionMandatoryWithSeparator, RepetitionWithSeparator, Rule, Terminal, VERSION, __esModule, clearCache, createSyntaxDiagramsCode, createToken, createTokenInstance, defaultLexerErrorProvider, defaultParserErrorProvider, isRecognitionException, serializeGrammar, serializeProduction, tokenLabel, tokenMatcher, tokenName)

So Webpack uses the ESM Version for bundling and does not find the default export from lib/src/api.js that is imported in api_esm.mjs. Ignoring the warnings and testing the language-server by starting the Argdown VSCode extension leads to an immediate crash.

If I make the following change in the first line of api_esm.mjs, the warnings during the build process disappear and the language server no longer crashes:

import * as mod from "../lib/src/api.js";

[christianvoigt]

Hi again, I finally solved my webpack issues today and quickly wanted to report my findings. The problem was caused by my webpack.config.js. For some reason (unknown to me) it contained the following problematic module rule:

  module: {
    rules: [
      {
        test: /\.mjs$/,
        type: "javascript/auto",
      },
     ]
   }

Removing this rule or changing the type to javascript/esm fixed the bundling issues with chevrotain.

[bd82]

I will close this for now. Feel free to re-open if needed