Module not found: Error: Package path ./highlight.min.js is not exported from package @highlightjs\cdn-assets #3223

masx200 · 2021-06-03T04:51:49Z

Describe the issue/behavior that seems buggy

Module not found: Error: Package path ./highlight.min.js is not exported from package D:\Documents\github\markdown-reader\node_modules@highlightjs\cdn-assets (see exports field in D:\Documents\github\markdown-reader\node_modules@highlightjs\cdn-assets\package.json)

Sample Code or Instructions to Reproduce

import hljs from "@highlightjs/cdn-assets/highlight.min.js";

export default hljs;

Expected behavior

Additional context

webpack 5.38.1
@highlightjs/cdn-assets 11.0.0

{
   "exports": {
      ".": {
         "require": "./lib/index.js",
         "import": "./es/index.js"
      },
      "./package.json": "./package.json",
      "./lib/common": {
         "require": "./lib/common.js",
         "import": "./es/common.js"
      },
      "./lib/core": {
         "require": "./lib/core.js",
         "import": "./es/core.js"
      },
      "./lib/languages/*": {
         "require": "./lib/languages/*.js",
         "import": "./es/languages/*.js"
      },
      "./scss/*": "./scss/*",
      "./styles/*": "./styles/*",
      "./types/*": "./types/*"
   }
}

masx200 · 2021-06-03T05:03:40Z


> require('@highlightjs/cdn-assets/highlight.min.js')
Uncaught:
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './highlight.min.js' is not defined by "exports" in D:\Documents\github\markdown-reader\node_modules\@highlightjs\cdn-assets\package.json
    at new NodeError (node:internal/errors:363:5)
    at throwExportsNotFound (node:internal/modules/esm/resolve:321:9)
    at packageExportsResolve (node:internal/modules/esm/resolve:546:3)
    at resolveExports (node:internal/modules/cjs/loader:478:36)
    at Function.Module._findPath (node:internal/modules/cjs/loader:518:31)
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:927:27)
    at Function.Module._load (node:internal/modules/cjs/loader:774:27)
    at Module.require (node:internal/modules/cjs/loader:1013:19)
    at require (node:internal/modules/cjs/helpers:93:18)
    at REPL4:1:1 {
  code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}

joshgoebel · 2021-06-03T05:07:59Z

Yeah this is a problem, certainly. Thanks for finding and filing all these issues, but curious - is there a reason you switched from the regular NPM package to cdn-assets now?

Right now I'm of the opinion that cdn-assets shouldn't have export restrictions at all (which would solve this)... but also most people bundling should probably be using the regular package (not con-assets) - so I'm truly curious why you're switching. :-)

masx200 · 2021-06-03T05:10:30Z

Yeah this is a problem, certainly. Thanks for finding and filing all these issues, but curious - is there a reason you switched from the regular NPM package to cdn-assets now?

Right now I'm of the opinion that cdn-assets shouldn't have export restrictions at all (which would solve this)... but also most people bundling should probably be using the regular package (not con-assets) - so I'm truly curious why you're switching. :-)

Because I want to use those built-in language modules directly.

masx200 · 2021-06-03T05:11:34Z

import hljs from "../node_modules/@highlightjs/cdn-assets/highlight.min.js";

I found that as long as it is imported in this way, it works normally.

joshgoebel · 2021-06-03T05:14:59Z

Because I want to use those built-in language modules directly.

I don't understand. You can use them directly with the regular NPM package - you don't need to use cdn-assets.

- Resolves highlightjs#3223

- Resolves #3223

joshgoebel · 2021-06-04T01:47:33Z

Resolved with release of 11.0.1.

Exports are no longer restricted for cdn-assets, as this was never the intention.

bitencode · 2021-07-14T15:47:20Z

Not sure this is really fixed yet - it also happens on regular npm package. I assume it's a problem here because 10.x works but 11.x does not - I don't have this issue with any other npm package. I migrated to 11.0.0 when it came out and had to roll back to latest 10.x because of this problem. I upgraded to 11.1.0 this morning and still have this issue.

dependencies:

"dependencies": {
  ...
  "highlight.js": "11.1.0",
  "markdown-it": "12.1.0",
  "markdown-it-attrs": "4.0.0",
  ...
}

imports:

import MarkdownIt from 'markdown-it';
import MarkdownItAttrs from 'markdown-it-attrs';
import hljs from 'highlight.js/lib/core';
import 'highlight.js/styles/github.css';

hljs.registerLanguage('json', require('highlight.js/lib/languages/json'));
hljs.registerLanguage('markdown', require('highlight.js/lib/languages/markdown'));
hljs.registerLanguage('python', require('highlight.js/lib/languages/python'));
hljs.registerLanguage('xml', require('highlight.js/lib/languages/xml'));
hljs.registerLanguage('yaml', require('highlight.js/lib/languages/yaml'));

attempt to lint (build same problem, but not from eslint obviously):

Oops! Something went wrong! :(

ESLint: 7.29.0

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './styles/github.css' is not defined by "exports" in /Users/johnm/src/sdvi/swarm/node_modules/highlight.js/package.json
    at throwExportsNotFound (internal/modules/esm/resolve.js:285:9)
    at packageExportsResolve (internal/modules/esm/resolve.js:491:3)
    at resolveExports (internal/modules/cjs/loader.js:444:36)
    at Function.Module._findPath (internal/modules/cjs/loader.js:484:31)
    at findModulePath (/Users/johnm/src/sdvi/swarm/node_modules/eslint-import-resolver-alias/index.js:99:27)
    at Object.exports.resolve (/Users/johnm/src/sdvi/swarm/node_modules/eslint-import-resolver-alias/index.js:75:10)
    at v2 (/Users/johnm/src/sdvi/swarm/node_modules/eslint-module-utils/resolve.js:117:23)
    at withResolver (/Users/johnm/src/sdvi/swarm/node_modules/eslint-module-utils/resolve.js:122:14)
    at fullResolve (/Users/johnm/src/sdvi/swarm/node_modules/eslint-module-utils/resolve.js:139:22)
    at Function.relative (/Users/johnm/src/sdvi/swarm/node_modules/eslint-module-utils/resolve.js:84:10)
error Command failed with exit code 2.

However, this works, but is not right:

import MarkdownIt from 'markdown-it';
import MarkdownItAttrs from 'markdown-it-attrs';
import hljs from 'highlight.js/lib/core';
import '../../node_modules/highlight.js/styles/github.css';

hljs.registerLanguage('json', require('../../node_modules/highlight.js/lib/languages/json'));
hljs.registerLanguage('markdown', require('../../node_modules/highlight.js/lib/languages/markdown'));
hljs.registerLanguage('python', require('../../node_modules/highlight.js/lib/languages/python'));
hljs.registerLanguage('xml', require('../../node_modules/highlight.js/lib/languages/xml'));
hljs.registerLanguage('yaml', require('../../node_modules/highlight.js/lib/languages/yaml'));

Edit
Actually, the ../../node_modules/ bit makes eslint work, but both my current webpack and rollup builds fail with the path specified.

dhruvkb · 2021-07-25T04:03:00Z

This seems to be broken for me as well. I'm getting the following error message:

Module not found: Error: Package path ./lib/languages is not exported from package <path_to_proj>/node_modules/highlight.js (see exports field in <path_to_proj>/node_modules/highlight.js/package.json)

This message appears when using the dynamic import syntax

await import(
  /*
   webpackInclude: /(java|javascript|latex|markdown|python|ruby|typescript|xml|yaml)/,
   webpackChunkName: "lang-[request]"
   */
   `highlight.js/lib/languages/${lang}.js`
)

The following are all solutions that fix the problem for me:

Removing the exports field from package.json
Adding one more export as follows:

     "./lib/languages/*": {
       "require": "./lib/languages/*.js",
       "import": "./es/languages/*.js"
     },
+    "./lib/languages": {
+      "require": "./lib/languages",
+      "import": "./es/languages"
+    },

Referencing from as a relative path from the project directory also works:

 await import(
   /*
    webpackInclude: /(java|javascript|latex|markdown|python|ruby|typescript|xml|yaml)/,
    webpackChunkName: "lang-[request]"
    */
-   `highlight.js/lib/languages/${lang}.js`
+   `@/../node_modules/highlight.js/lib/languages/${lang}.js`
 )

Downgrading to v10. This isn't really a solution but it used to work before so, as this works as a last resort.

Downgrading to the latest v10 release fixes this problem for me. Removing the exports from v11 also fixes the problem. So something about the exports key in the package.json for v11 has to be the cause.

Framework: Vue 3 (Vue CLI 5)
Language: TypeScript
Bundler: Webpack 5
Node: 14
npm: 7

joshgoebel · 2021-07-25T06:49:41Z

There is never any reason to directly import lib/languages (there is nothing there, no index, etc) only files within that folder, which the wildcard subpath pattern should already cover. Having to specify the top-level directory in exports also seems broken and entirely redundant to me. I can find no indication in the documentation that subpath patterns should not be sufficient. Subpath folder mappings (as suggested above) are also deprecated...

https://nodejs.org/api/packages.html#packages_subpath_patterns

Perhaps file an issue against Webpack if that is what is kicking up the error?

dhruvkb · 2021-07-25T17:35:51Z

I did not import the lib/languages folder, I'm importing individual language files (by using a dynamic import expression). I'm quite confused by this error myself. The workarounds also seem to work without any reason or explanation.

joshgoebel · 2021-07-25T18:02:55Z

I realize that. That's why I suggested file a bug against your packaging software. Of course you can link to this issue and we'll see where things land.

azul · 2021-10-27T21:50:35Z

Using a separate variable to store the module name seems to have fixed this for me.
So instead of

await import(
  /*
   webpackInclude: /(java|javascript|latex|markdown|python|ruby|typescript|xml|yaml)/,
   webpackChunkName: "lang-[request]"
   */
   `highlight.js/lib/languages/${lang}.js`
)

you would use:

const moduleName = `highlight.js/lib/languages/${lang}.js`
await import(
  /*
   webpackInclude: /(java|javascript|latex|markdown|python|ruby|typescript|xml|yaml)/,
   webpackChunkName: "lang-[request]"
   */
   moduleName
)

I have no idea why and if this actully works. Fixes my build and the example in the webpack issue though.

joshgoebel · 2021-10-27T21:57:55Z

I wonder though if you changed your import from build-time to run-time since now the optimizer isn't smart enough to know the string at compile time?

azul · 2021-10-28T10:56:18Z

I wonder though if you changed your import from build-time to run-time since now the optimizer isn't smart enough to know the string at compile time?

That may have been the effect... but how would the compiler be smart enough to know lang at compile time? I think it should have imported at run-time anyway but tried at compile time never the less which led to the error because lang was empty at compile time.

(I don't really understand what's going on here - just guessing)

joshgoebel · 2021-10-28T13:00:17Z

Sorry, no idea. Thanks for sharing though.

masx200 added bug help welcome Could use help from community parser labels Jun 3, 2021

joshgoebel added a commit to joshgoebel/highlight.js that referenced this issue Jun 4, 2021

(fix) do not restrict exports from cdn-assets

a672b82

- Resolves highlightjs#3223

joshgoebel added a commit that referenced this issue Jun 4, 2021

(fix) do not restrict exports from cdn-assets

9268dc2

- Resolves #3223

joshgoebel closed this as completed Jun 4, 2021

joshgoebel mentioned this issue Jul 14, 2021

Can't import styles #3275

Closed

dhruvkb mentioned this issue Jul 26, 2021

Dynamic imports don't work when exports specified in package.json and aliases webpack/webpack#13865

Open

juliusknorr mentioned this issue Oct 27, 2021

Bump highlight.js from 10.7.3 to 11.3.1 nextcloud/text#1901

Closed

azul mentioned this issue Oct 27, 2021

Package path ./lib/languages is not exported from package - breaks import with webpackChunkName #3376

Closed

azul mentioned this issue Nov 2, 2021

exports in package.json break dynamic imports with webpack #3384

Closed

StanislavByzov mentioned this issue Nov 9, 2021

webpack import(@angular/common/locales/${mylocale}) not working angular/angular-cli#22088

Closed

Rambou mentioned this issue Nov 12, 2021

Dynamic import of locales not available in Angular 13 angular/angular-cli#22154

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Module not found: Error: Package path ./highlight.min.js is not exported from package @highlightjs\cdn-assets #3223

Module not found: Error: Package path ./highlight.min.js is not exported from package @highlightjs\cdn-assets #3223

masx200 commented Jun 3, 2021 •

edited

Loading

masx200 commented Jun 3, 2021

joshgoebel commented Jun 3, 2021

masx200 commented Jun 3, 2021

masx200 commented Jun 3, 2021

joshgoebel commented Jun 3, 2021

joshgoebel commented Jun 4, 2021

bitencode commented Jul 14, 2021 •

edited

Loading

dhruvkb commented Jul 25, 2021 •

edited

Loading

joshgoebel commented Jul 25, 2021 •

edited

Loading

dhruvkb commented Jul 25, 2021 •

edited

Loading

joshgoebel commented Jul 25, 2021

azul commented Oct 27, 2021

joshgoebel commented Oct 27, 2021 •

edited

Loading

azul commented Oct 28, 2021

joshgoebel commented Oct 28, 2021 •

edited

Loading

Module not found: Error: Package path ./highlight.min.js is not exported from package @highlightjs\cdn-assets #3223

Module not found: Error: Package path ./highlight.min.js is not exported from package @highlightjs\cdn-assets #3223

Comments

masx200 commented Jun 3, 2021 • edited Loading

masx200 commented Jun 3, 2021

joshgoebel commented Jun 3, 2021

masx200 commented Jun 3, 2021

masx200 commented Jun 3, 2021

joshgoebel commented Jun 3, 2021

joshgoebel commented Jun 4, 2021

bitencode commented Jul 14, 2021 • edited Loading

dhruvkb commented Jul 25, 2021 • edited Loading

joshgoebel commented Jul 25, 2021 • edited Loading

dhruvkb commented Jul 25, 2021 • edited Loading

joshgoebel commented Jul 25, 2021

azul commented Oct 27, 2021

joshgoebel commented Oct 27, 2021 • edited Loading

azul commented Oct 28, 2021

joshgoebel commented Oct 28, 2021 • edited Loading

masx200 commented Jun 3, 2021 •

edited

Loading

bitencode commented Jul 14, 2021 •

edited

Loading

dhruvkb commented Jul 25, 2021 •

edited

Loading

joshgoebel commented Jul 25, 2021 •

edited

Loading

dhruvkb commented Jul 25, 2021 •

edited

Loading

joshgoebel commented Oct 27, 2021 •

edited

Loading

joshgoebel commented Oct 28, 2021 •

edited

Loading