kchindam-infy

@sudo-barun Thanks for the detailed steps, its generally recommended to initialize a project using npm init -y to create a proper package.json with a name field. This avoids the inconsistency...

HI @falk-stefan Could you share private package for @tapntour so that i can quickly try to troubleshoot the issue to find the RC.

introduced malformed token in npmrc config and tried it with latest node and npm version could not reproduce the issue, checked both the terminal output and details logs. Have you...

@sethtomy I tried the npm ls and all the dependencies and devDependencies are listed as expected. If you still think this is an issue, please provide more details to troubleshoot.

@sethtomy

HI @DanielLey21 To better understand the issue, could you please provide your npm config details. Please make sure to mask any sensitive information. you can replace sensitive information by [MASKED]...

@bkuhlmann Thanks for the npm config, ofcourse i have tried with similar config with npm registry and authToken. On npm login command on Press Enter key it successfully launched the...

Hi @dylan-conway Thanks, could you share the package.json configuration, specifically any bin fields setup? WIll help us to understand how the project is structured and if it has any influence...

**Closing:** this looks to be similar if not a duplicate of an existing issue, #7585. If you believe your instance is unique, please provide further clarifying details.

Unable to reproduce the issue as [email protected] . Tried on the environment as mentioned. I have tried with lodash and micromatch packages and the audited json output is looking good...