deno publish
should be more lenient with calls to require
functions
#27986
Labels
publish
Related to "deno publish" subcommand
Version: Deno 2.1.7
I'm trying to publish some packages to JSR, and I have
@babel-test-6ae45912/preset-typescript
that depends on@babel-test-6ae45912/helper-plugin-utils
@babel-test-6ae45912/helper-plugin-utils
that depends on@babel-test-6ae45912/core
@babel-test-6ae45912/core
that contains the file below:Deno/JSR detects this file as depending on
@babel-test-6ae45912/preset-typescript
, and thus the publishing process fails witherror: Circular package dependency detected: @babel-test-6ae45912/core -> @babel-test-6ae45912/preset-typescript -> @babel-test-6ae45912/helper-plugin-utils -> @babel-test-6ae45912/core
.In the cycles detection logic, it should probably either:
require()
calls in ESM files, since ESM does not have the "global" CJSrequire()
require()
calls that are calling functions namedrequire
declared in scope, since they are not the "global" CJSrequire()
require()
calls, since JSR does not support CJS anyway and it will already throw an error when you try to publish a CJS fileThe text was updated successfully, but these errors were encountered: