AdminLTE v4.0.0-rc1

[puikinsh]

AdminLTE v4.0.0-rc1 - Major Modernization Release

This release represents a complete modernization of the AdminLTE codebase, bringing it up to current standards with the latest tooling, dependencies, and best practices.

Key Highlights

• Zero Security Vulnerabilities - All dependencies updated and vulnerabilities resolved
• Modern Tooling - ESLint v9, Astro 5.x, latest Stylelint and build tools
• Better Developer Experience - New npm start command, improved scripts, cleaner builds
• Latest Dependencies - Bootstrap 5.3.7, Node.js ES modules, 50+ package updates
• Code Quality - Zero linting errors, removed technical debt, standardized formatting
• Future-Ready - Modern configuration patterns, optimal bundle sizes, enhanced maintainability

Quick Start

# Install dependencies
npm install

# Start development server
npm start

# Build for production  
npm run production

Major Changes

Infrastructure & Tooling

• Upgraded to ES Modules with "type": "module" in package.json
• Complete ESLint v9 migration with modern flat configuration format
• Enhanced Astro configuration with static site generation
• Optimized build scripts and developer experience

Dependencies Updated

• astro: 4.15.12 → 5.10.0
• eslint: 8.57.1 → 9.29.0
• bootstrap: 5.3.3 → 5.3.7
• sass: 1.78.0 → 1.89.2
• typescript: 5.6.2 → 5.8.3
• Plus 50+ other packages updated to latest versions

Security & Quality

• Resolved all npm security vulnerabilities (0 remaining)
• Updated browserslist database for modern browser compatibility
• Fixed all SASS deprecation warnings
• Zero linting errors across all file types

Migration Guide

For Users:

• No breaking changes in compiled CSS/JS output
• All existing HTML templates remain fully compatible
• CDN links and package imports work as before

For Developers:

• New npm start command for development
• ESLint configuration migrated to eslint.config.js
• Build process requires Node.js ES modules support

Compatibility

• Bootstrap: 5.3.7 (latest)
• Node.js: ES modules support required
• Browsers: All modern browsers supported
• RTL: Full right-to-left language support maintained

See CHANGELOG.md for complete technical details.

---

Download: Use npm: npm install [email protected] or download the source code below.

---

This discussion was created from the release AdminLTE v4.0.0-rc1.

[saiwal]

Is there a demo somewhere?

[puikinsh]

@dfsmania

Thanks for reporting this. dist/ folder is back on the repo
Demo is available here: https://adminlte-v4.netlify.app/dist/index.html
And here: https://adminlte.io/themes/v4/index.html

Dev/production should run smoothly with the dist/ folder in place.

Let me know if you find anything else that needs fixing, and sorry again for not committing dist/ folder.

[dfsmania]

There's no problem, you're doing a good job bringing this package back to life!

So far, all good now. Just a minor organization note on the dist folder, previously, all html build files were placed inside dist/pages folder and now they are dropped just in dist. I'll share a screenshot of how it looked like on beta3:

[dfsmania]

@puikinsh When you get some time, could you please check my previous comment, and then release a new rc3 version of the package? The latest release rc1 doesn't work as expected and the latest changes you had introduced at least gets the package to a more stable version... Thanks!

[puikinsh]

What are the advantages of retaining the /pages folder? Are there existing implementations that depend on it, or are there other reasons to keep it? I'm open to reinstating it, but I'd like to understand the rationale. Note: RC3 dist folder will be available soon.

[dfsmania]

@puikinsh From my point of view, it's just organization, so all the demo pages are dropped inside a same folder, you can call it pages, demo, demo_pages or whatever you like. I'm not sure if there is another issue other than organization, since I'm just using the compiled and minimized files on the projects I'm working on. If having this structure on the dist folder breaks something else, just let as it is now, it was just an organization enhancement, at least for me...

[byc0d3]

Saludos, gracias por mantener este proyecto, a todosssss, la version final se espera para cuando ?