fix: total purge of Next.js slop and NPM artifacts#4
Closed
hyperpolymath wants to merge 1 commit into
Closed
Conversation
Owner
hyperpolymath
commented
Mar 3, 2026
hyperpolymath
commented
- Deleted all Next.js configuration and source code
- Removed all residual NPM/PNPM/Yarn lockfiles
- Established clean ReScript + Deno + Vanilla CSS UI baseline
- Terminated all Next.js-related security vulnerabilities
hyperpolymath
force-pushed
the
security/de-slop-and-harden
branch
2 times, most recently
from
85b703f to
726e5a7
Compare
hyperpolymath
force-pushed
the
security/de-slop-and-harden
branch
from
820ca0f to
0945311
Compare
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.