ESLintIgnoreWarning: The ".eslintignore" file is no longer supported. Switch to using the "ignores" property in "eslint.config.js": https://eslint.org/docs/latest/use/configure/migration-guide#ignoring-files
(Use `node --trace-warnings ...` to show where the warning was created)
No warnings. No .eslintignore file should be generated.
Screenshots
Which versions of Sanity are you using?
@sanity/cli (global) 3.14.4 (latest: 3.44.0)
@sanity/incompatible-plugin 1.0.4 (up to date)
@sanity/pkg-utils 6.8.18 (up to date)
@sanity/plugin-kit 4.0.16 (up to date)
sanity 3.44.0 (up to date)
What operating system are you using?
Mac
Which versions of Node.js / npm are you running?
pnpm 9.0.5
Additional context
Add any other context about the problem here.
Security issue?
Any security issues should be submitted directly to security@sanity.io. In order to determine whether you are dealing with a security issue, ask yourself these two questions:
Can I access something that's not mine, or something I shouldn't have access to?
Can I disable something for other people? If the answer to either of those two questions are "yes", then you're probably dealing with a security issue. Note that even if you answer "no" to both questions, you may still be dealing with a security issue, so if you're unsure, just email us at [security@sanity.io](mailto:security@sanity.io.
Describe the bug
To Reproduce
Steps to reproduce the behavior:
pnpx @sanity/plugin-kit@latest verify-package
Expected behavior
No warnings. No .eslintignore file should be generated.
Screenshots
Which versions of Sanity are you using?
@sanity/cli (global) 3.14.4 (latest: 3.44.0) @sanity/incompatible-plugin 1.0.4 (up to date) @sanity/pkg-utils 6.8.18 (up to date) @sanity/plugin-kit 4.0.16 (up to date) sanity 3.44.0 (up to date)
What operating system are you using?
Mac
Which versions of Node.js / npm are you running?
pnpm 9.0.5
Additional context
Add any other context about the problem here.
Security issue?
Any security issues should be submitted directly to security@sanity.io. In order to determine whether you are dealing with a security issue, ask yourself these two questions: