Skip to content
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.

Sign up for GitHub

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

Jump to bottom

feat: add strictOptions to config to toggle --strict checks #724

Merged
merged 1 commit into from
Apr 11, 2024
Merged

feat: add strictOptions to config to toggle --strict checks #724

merged 1 commit into from
Apr 11, 2024
+330 −21

Conversation

stipsan
Copy link
Member

@stipsan stipsan commented Apr 11, 2024

No description provided.

@stipsan stipsan requested a review from a team as a code owner April 11, 2024 18:36
@stipsan stipsan force-pushed the configure-strict-mode branch 2 times, most recently from f736023 to 79c90f0 Compare April 11, 2024 19:01
@socket-security Socket Security
Copy link

socket-security bot commented Apr 11, 2024 •
edited
Loading

New dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/next@14.1.4 environment, filesystem, network, shell, unsafe +5 88.8 MB vercel-release-bot
npm/npm-run-all2@6.1.2 environment, filesystem Transitive: shell +6 738 kB bret

View full report↗︎

@stipsan stipsan force-pushed the configure-strict-mode branch 2 times, most recently from d5d58ac to adf31df Compare April 11, 2024 19:16
@stipsan stipsan force-pushed the configure-strict-mode branch from adf31df to 1fc0807 Compare April 11, 2024 19:20
@stipsan stipsan merged commit 396ce6c into main Apr 11, 2024
9 checks passed
@stipsan stipsan deleted the configure-strict-mode branch April 11, 2024 19:24
This was referenced Apr 11, 2024
Closed
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@stipsan