-
Notifications
You must be signed in to change notification settings - Fork 507
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
can this node-gyp warning be dealt with? #962
Comments
I have never used yarn, but to me it seems the warning comes from yarn and not from node-gyp. According to the [yarn documentation](https://yarnpkg.com/configuration/yarnrc#logFilters), you can set a logFilter in .yarnrc to suppress it.
…On November 13, 2023 6:21:08 PM GMT+02:00, Eric ***@***.***> wrote:
I am using node 18.18.2 and yarn 3.2.4.
If I do:
1. mkdir test
2. cd test
3. yarn init
4. yarn add nan
I get the warning:
```
➤ YN0032: │ ***@***.***:2.18.0: Implicit dependencies on node-gyp are discouraged
```
I aim for zero-warnings because unimportant warnings make it hard to notice important warnings.
Can this warning be dealt with?
|
Ok. Still seems like it is a good recommendation. You may want to reconsider the implicit dependency. Feel free to close this issue if you know otherwise or keep it open as a reminder to investigate further. |
Cannot do that. They are intentionally pinned to specific versions since nothing else works across the board.
…On November 13, 2023 9:44:08 PM GMT+02:00, Eric ***@***.***> wrote:
Ok. Still seems like it is a good recommendation. You may want to reconsider the implicit dependency. Feel free to close this issue if you know otherwise or keep it open as a reminder to investigate further.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am using node 18.18.2 and yarn 3.2.4.
If I do:
I get the warning:
I aim for zero-warnings because unimportant warnings make it hard to notice important warnings.
Can this warning be dealt with?
The text was updated successfully, but these errors were encountered: