marked.esm is using a default export instead of a named export. so the proper syntax would be:

import marked from 'marked' // note that this is a definition, so you can give it any name you want

But i think you are raising an important point: Why was a default export chosen over a named export? It removes many of the advantages of using esm. As the result is still just some convoluted mess of properties.

It would be much more userfriendly with well organized named exports as they work excellently with TS-language-features.

I'll file a seperate issue about that in a bit

I tried that syntax as well, but errors with "'default' is not exported by node_modules/marked/lib/marked.js" detail below:

bundles src/main.js → public/build/bundle.js... (!) thishas been rewritten toundefined https://rollupjs.org/guide/en/#error-this-is-undefined node_modules/marked/lib/marked.js 14: typeof define === 'function' && define.amd ? define(factory) : 15: (global = global || self, global.marked = factory()); 16: }(this, (function () { 'use strict'; ^ 17: 18: function _defineProperties(target, props) { [!] Error: 'default' is not exported by node_modules/marked/lib/marked.js, imported by src/parser/parser.js https://rollupjs.org/guide/en/#error-name-is-not-exported-by-module src/parser/parser.js (10:7) 8: 9: /*************** Imports *****************/ 10: import marked from 'marked';'

Looking at lib/marked.esm.js#L2356 it exports default, but if I try
import marked from 'marked_esm';
that errors with
(!) Unresolved dependencies https://rollupjs.org/guide/en/#warning-treating-module-as-external-dependency marked_esm (imported by src/parser/parser.js) (!) Missing global variable name Use output.globals to specify browser global variable names corresponding to external modules marked_esm (guessing 'marked')
and in my js I get

Uncaught ReferenceError: marked is not defined

with
marked.lexer('# heading');

have you tried import marked from "marked/lib/marked.esm.js";?

I don't usually use esm since it is still experimental in node. If anyone wants to create a PR I would be happy to review it.

Here's the usage

import Marked from '../node_modules/marked/lib/marked.esm.js'

Marked(rawMarkdown)

I'm using it in the <wc-markdown> web component

cjs-require/esm-import can be automatically handled by specifying an "exports" field in the package.json.
This way node will load the appropriate files without the user having to worry about in-module paths.

Short explanation

{
  "exports": {
    [exportPath]: {
      "import": "./path/to/file.mjs",
      "require": "./path/to/file.cjs"
    }
  }
}

So for marked it would be:

{
  "exports": {
    ".": {
      "import": "./lib/marked.esm.mjs", // `.mjs`-extention is needed
      "require": "./src/marked.js"
    }
  }
}

I'll file a PR for that shortly