(Regression) Published scoped npm packages gets wrong path using JF CLI

[rimanov]

Describe the bug

This bug report is opened as a regression of the bug here: #2280

Creating and publishing a scoped NPM package via JFrog CLI results in the artifact being uploaded under the wrong path.

Current behavior

This issue was reported and "fixed" per #2280, however, it looks like the behavior is a regression as we're able to reproduce with the latest JFrog CLI version 2.73.3

Reproduction steps

1. Create scoped npm package.

jf npm publish
15:15:42 [🔵Info] Running npm Publish
npm notice
npm notice 📦 @rasul/[email protected]
npm notice Tarball Contents
npm notice 81B index.js
npm notice 218B package.json
npm notice Tarball Details
npm notice name: @rasul/my-test-package
npm notice version: 1.0.0
npm notice filename: rasul-my-test-package-1.0.0.tgz
npm notice package size: 334 B
npm notice unpacked size: 299 B
npm notice shasum: 9c349bdb0dc0e3b86eed29126e4551f1d1ac42e3
npm notice integrity: sha512-H6sku0VlCivMw[...]F1a2kUtYd9flw==
npm notice total files: 2
npm notice
15:15:43 [🔵Info] [Thread 2] Uploading: /Users/rasuli/my-test-package/rasul-my-test-package-1.0.0.tgz
15:15:45 [🔵Info] npm publish finished successfully.
15:15:45 [🔵Info] These files were uploaded:

📦 rasuli-npm-local
└── 📁 @rasul
└── 📁 my-test-package
└── 📁 -
└── 📁 @rasul
└── 📄 my-test-package-1.0.0.tgz

{
"status": "success",
"totals": {
"success": 1,
"failure": 0
}
}

This results in the artifact being published in the below path:

Expected behavior

We expect the extra scope name to not be included for the second time in the path per NPM.

JFrog CLI version

2.73.3

Operating system type and version

MacOS, Linux

JFrog Artifactory version

latest

JFrog Xray version

na

[fluxxBot]

@rimanov This is the expected behavior as per JFrog Artifactory. Even if you use the regular npm client for the same operation, you will observe a similar pattern. Could you share more details on why do you think the path is wrong?

We will wait for your response for four days before closing the issue since this does not appear to be a bug. However, feel free to reopen or reach out if you believe this is still an issue for you.