Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[BUG] init.author.name deprecation warning does not stop #4840

Closed
2 tasks done
sourabhv opened this issue May 3, 2022 · 4 comments
Closed
2 tasks done

[BUG] init.author.name deprecation warning does not stop #4840

sourabhv opened this issue May 3, 2022 · 4 comments
Labels
Bug thing that needs fixing Needs Discussion is pending a discussion Needs Triage needs review for next steps Release 8.x work is associated with a specific npm 8 release

Comments

@sourabhv
Copy link

sourabhv commented May 3, 2022

Is there an existing issue for this?

  • I have searched the existing issues

This issue exists in the latest npm version

  • I am using the latest npm

Current Behavior

$ cat ~/.npmrc
init-author-name=<name>
init-author-email=<email>
init-author-url=<url>

$ npm i 
npm WARN config init.author.name Use `--init-author-name` instead.

The init.author.name warning is still there

Expected Behavior

Warning init.author.name should stop like other 2.

Steps To Reproduce

  1. In this environment...
    Mac OS Monterey on Macbook Pro 16 2021
    Node v18.0.0 installed via brew
    NPM v8.8.0

  2. With this config...

    init-author-name="Foo bar"
    init-author-email=foo.bad@gmail.com
    init-author-url=https://github.com/foobar

  3. Run
    npm i

  4. See error:
    npm WARN config init.author.name Use --init-author-name instead.

Environment

  • npm:
  • Node.js:
  • OS Name:
  • System Model Name:
  • npm config:
; copy and paste output from `npm config ls` here
@sourabhv sourabhv added Bug thing that needs fixing Needs Triage needs review for next steps Release 8.x work is associated with a specific npm 8 release labels May 3, 2022
@wraithgar
Copy link
Member

Please fill out this issue completely. Of particular importance is the output from npm config ls as it may give us clues as to what is happening here.

@wraithgar wraithgar added the Needs Discussion is pending a discussion label May 3, 2022
@sourabhv
Copy link
Author

sourabhv commented May 3, 2022

This might sound weird, but I removed the brew version and installed from nvm and it works fine now. Closing, not sure why it was happening.

@sourabhv sourabhv closed this as completed May 3, 2022
@calocaleta
Copy link

Hi, I use VSCode and edit the lines as the warning say:

code /home/MYUSER/.npmrc

I replace line 14:
init-author-email=<email>
or
init.author.email=<email>

instead:
--init-author-email=<email>

and works fine.

@SamuuX
Copy link

SamuuX commented Jul 31, 2022

Hola, uso VSCode y edito las líneas como dice la advertencia:

code /home/MYUSER/.npmrc

Reemplazo la línea 14: init-author-email=<email> o init.author.email=<email>

en cambio: --init-author-email=<email>

y funciona bien

A mí también me funciono / it worked for me too

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Bug thing that needs fixing Needs Discussion is pending a discussion Needs Triage needs review for next steps Release 8.x work is associated with a specific npm 8 release
Projects
None yet
Development

No branches or pull requests

4 participants