v2.1.8: Dependency Injection Refactor & Security Hardening

refactor: remove fs/path from core via Context Object injection and add explicit Guard Clause validation

v2.1.7: Web GUI Update

feat: implement web application with markdown preview, editor, and terminal panels

v2.1.5

🚀 Release Notes (v2.1.5)

This release focuses on a massive overhaul of our documentation and developer experience (DX), ensuring that both first-time users and core contributors have the smoothest experience possible.

There are no breaking changes or new CLI features in this release. It is a 100% safe, documentation-only update!

📚 Documentation

• Purpose-Driven Installation Guide: Completely redesigned the installation sections in README.md and USAGE.md. The guide is now perfectly structured based on user intent (e.g., "Execute directly with npx" vs "Install globally with npm").
• Fully Responsive UI: Removed legacy Markdown tables from the documentation in favor of a modern, responsive layout ([Heading + Code Block + Bullet points]). This completely eliminates horizontal scrolling issues on mobile devices and npmjs.com, and works perfectly with GitHub's native "Copy" buttons.
• npm vs npx Clarification: Added a beginner-friendly "Prerequisite" section that clearly explains the core differences between package management (npm) and package execution (npx), eliminating a common source of confusion.
• IDE "Gotchas" Resolved: Explicitly documented the command not found pitfall when installing locally (without -g) inside VS Code, providing exact workarounds (npx splist or npm run).

🛡️ Developer Experience & CI

• Implementation of a Robust Release Workflow: A new contributor guide outlining a five-step error-free release process.

• Addition of Status Badges: Dynamic GitHub Actions (public status) and GitHub repository badges have been added to the beginning of the README. This provides users with real-time information about the project's health, increasing credibility.

Other features include local environment cl etc.

---

Full Changelog: v2.1.4...v2.1.5

---

v2.1.3 - Security: Remove child_process and process.env

🛡️ Security & Refactoring

• Security: Removed child_process (exec) from phase4.js to eliminate Shell Access risk alerts on Socket.dev.
• Security: Removed process.env reading from phase2.js to eliminate Environment Variable access alerts on Socket.dev.
• Bump: Updated package version to 2.1.3.

Full Changelog: v2.1.2...v2.1.3

v2.1.2 - Docs: README and Installation Guide Updates

📝 What's Changed

• Documentation: Updated the README.md to feature the recommended
  pm install -g @splists/splist installation method.
• Documentation: Added clear instructions on how users can verify their installation via the splist -v command.
• Cleanup: Removed broken image links from the top of the README.

Full Changelog: v2.1.1...v2.1.2

v2.1.1 - Hotfix: Version check support

🔧 What's Changed (Hotfix)

• Fixed an issue where running splist -v or splist --version returned a File not found error.
• Added a helpful note clarifying the actual usage of the -v flag (which is used for folder conflict resolution during file processing).
• Closes #3

v2.1.0 - BROWSER UI Redesign

Overview

The Web GUI (SPLIST BROWSER) interface has been revamped with a full-fledged "VS Code-like" layout to allow users to operate it more intuitively, faithfully reproducing the feel of using a CLI tool in a browser.

Main Changes

• VS Code-like Layout:

• A new left sidebar (Activity Bar & Explorer) has been added to allow for easy management of input files and split output files in a tree format.

• The name "Web IDE" has been changed to "BROWSER," and text throughout the UI has been adjusted.

• Reproduction of a Real CLI Experience (UX):

• The run button that was at the bottom of the editor has been removed, and a "RUN (Enter)" button has been placed in the terminal panel. This achieves a realistic feel as if you were typing commands.

• The automatic processing that occurred during drag-and-drop and demo selection has been removed, and it has been modified so that users can select their desired options before clicking "RUN."

• Support for Multiple Input Files:

• Now allows you to load and test both README.md and USAGE.md with a single click from the sidebar by default.

• Now automatically adds files to the sidebar list when users drag and drop their own files.

• Other Improvements:

• Fixed the version notation in the header (V2.0.0) to be synchronized with package.json.

• Added a larger link and explanation to the root README.md to encourage access to the browser version (GitHub Pages).

• Resolved conflicts with upstream/main locally and synchronized to the latest state.

how to use

Notes

Tested using local build (npm run build).
After merging, the latest BROWSER environment will be automatically deployed to GitHub Pages.