Skip to content

Fix security vulnerability: Replace node-sass with sass#149

Open
master3395 wants to merge 2 commits intoFlynntes:masterfrom
master3395:master
Open

Fix security vulnerability: Replace node-sass with sass#149
master3395 wants to merge 2 commits intoFlynntes:masterfrom
master3395:master

Conversation

@master3395
Copy link
Contributor

- Replace vulnerable node-sass (^4.12.0) with sass (^1.80.0)
- Fixes qs package vulnerabilities (Prototype Pollution and DoS via arrayLimit bypass)
- Update npm scripts to use new sass CLI syntax
- Add build script for production builds
- Resolves security vulnerabilities Flynntes#47 and Flynntes#48
…irect

PR Flynntes#48: Uppercase headings and placeholders using CSS
- Change HTML placeholders from uppercase to lowercase for better accessibility
- Add CSS text-transform: uppercase for headings (.sleeky-heading)
- Add CSS text-transform: uppercase for input placeholders (.sleeky-input)
- Update SCSS with cross-browser placeholder support
- Compile updated styles.css

Issue Flynntes#35: Fix blank page after login redirect
- Add redirect_location filter to clean admin redirect URLs
- Remove trailing ? and .php extensions from redirect URLs
- Prevent double slashes in redirect URLs
- Fixes blank page issue after successful login

Resolves: Flynntes#35, Flynntes#48
HEAD;
}

// Fix login redirect URL to prevent blank page after login (Issue #35)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, how about separating this into it's own PR?

text-transform: uppercase;
}

// PR #48: Uppercase headings and placeholders using CSS
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like the same suggestion from above can be applied here

@Aternus
Copy link

Aternus commented Jan 5, 2026

@master3395 Looks like there is more content in the PR than what the PR description says, how about updating it to reflect that or separating the content into different PRs?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants