Generated .tgz file for JavaScript package is not yarn-installable

[climbertjh]

Describe the bug

When using JSII to generate/package JavaScript packages, the generated filename for the .tgz file is of the form <package-name>@<version>.jsii.tgz for the JavaScript code. The generated filename for the Python module is, by contrast, <module-name>-<version>.tar.gz.

The JavaScript package file, with the @ sign in the filename is not installable using yarn. yarn add file:<filename> results in errors during the add/install of the package.

Expected Behavior

Expected behavior is that the .tgz file created by the JavaScript packaging is installable (by filename reference) when using yarn add.

Current Behavior

After building the package file, yarn add fails with messages similar to:

yarn add file:../ncfour/projen-utils/dist/js/[email protected]
yarn add v1.22.21
info No lockfile found.
[1/4] Resolving packages...
error Package "file:../ncfour/projen-utils/dist/js/projen-utils" refers to a non-existing file '"/home/tjh/Projects/repos/testing/ncfour/projen-utils/dist/js/[email protected]"'.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

Reproduction Steps

1. Build a package using the JSII tools.
2. Create another project/package and initialize with yarn init
3. Attempt to install the package into the test project/package using yarn add

Possible Solution

Change the @ character in the generated filename to a - character.

Additional Information/Context

No response

SDK version used

5.3.23

Environment details (OS name and version, etc.)

WSL2 - Ubuntu

[climbertjh]

I have submitted a PR as a suggested update: #4449 .

[climbertjh]

I am canceling/closing PR #4449 .

I re-configured my projen projects to use npm rather than yarn ("Classic", v1.x.x) and have found that the package file name works OK when using npm as packageManager.