kaelum 1.4.6 → 1.4.8

package/README.md

@@ -1,6 +1,6 @@
 <div align="center">
 
-<img src="docs/public/logo-black.svg" alt="Kaelum" width="120" />
+<img src=".github/logo.svg" alt="Kaelum" width="120" />
 
 <h1>Kaelum</h1>
 
@@ -231,9 +231,9 @@ npm run format  # format code with Prettier
 
 ## 🤝 Contributing
 
-We welcome contributions! Please read our [Contributing Guide](CONTRIBUTING.md) before submitting a PR.
+We welcome contributions! Please read our [Contributing Guide](https://github.com/kaelumjs/.github/blob/main/CONTRIBUTING.md) before submitting a PR.
 
-See also: [Code of Conduct](CODE_OF_CONDUCT.md) · [Security Policy](SECURITY.md)
+See also: [Code of Conduct](https://github.com/kaelumjs/.github/blob/main/CODE_OF_CONDUCT.md) · [Security Policy](https://github.com/kaelumjs/.github/blob/main/SECURITY.md)
 
 ---
 

package/eslint.config.mjs

@@ -33,7 +33,6 @@ export default [
   {
     ignores: [
       "node_modules/",
-      "docs/",
       "coverage/",
       "cli/templates/",
       "*.config.js",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kaelum",
-  "version": "1.4.6",
+  "version": "1.4.8",
   "description": "A minimalist Node.js framework for building web pages and APIs with simplicity and speed.",
   "main": "index.js",
   "types": "index.d.ts",
@@ -17,9 +17,7 @@
     "test": "node --experimental-vm-modules node_modules/jest/bin/jest.js --verbose",
     "test:coverage": "node --experimental-vm-modules node_modules/jest/bin/jest.js --coverage",
     "lint": "eslint .",
-    "format": "prettier --write .",
-    "release": "standard-version",
-    "changelog": "standard-version --skip.bump --skip.tag --skip.commit"
+    "format": "prettier --write ."
   },
   "funding": {
     "type": "ko-fi",
@@ -45,7 +43,7 @@
   "bugs": {
     "url": "https://github.com/kaelumjs/kaelum/issues"
   },
-  "homepage": "https://github.com/kaelumjs/kaelum#readme",
+  "homepage": "https://kaelumjs.vercel.app/",
   "dependencies": {
     "cors": "^2.8.5",
     "dotenv": "^17.2.3",
@@ -61,7 +59,6 @@
     "eslint-config-prettier": "^10.1.8",
     "jest": "^30.2.0",
     "prettier": "^3.8.1",
-    "standard-version": "^9.5.0",
     "supertest": "^7.2.2"
   }
 }

package/.versionrc.js

@@ -1,20 +0,0 @@
-module.exports = {
-  infile: 'docs/misc/changelog.md',
-  types: [
-    { type: 'feat', section: 'Features' },
-    { type: 'fix', section: 'Bug Fixes' },
-    { type: 'perf', section: 'Performance Improvements' },
-    { type: 'revert', section: 'Reverts' },
-    { type: 'docs', section: 'Documentation', hidden: false },
-    { type: 'style', section: 'Styles', hidden: true },
-    { type: 'chore', section: 'Miscellaneous', hidden: false },
-    { type: 'refactor', section: 'Code Refactoring', hidden: false },
-    { type: 'test', section: 'Tests', hidden: true },
-    { type: 'build', section: 'Build System', hidden: true },
-    { type: 'ci', section: 'CI/CD', hidden: true },
-  ],
-  commitUrlFormat: '{{host}}/{{owner}}/{{repository}}/commit/{{hash}}',
-  compareUrlFormat: '{{host}}/{{owner}}/{{repository}}/compare/{{previousTag}}...{{currentTag}}',
-  issueUrlFormat: '{{host}}/{{owner}}/{{repository}}/issues/{{id}}',
-  userUrlFormat: '{{host}}/{{user}}'
-};

package/CODE_OF_CONDUCT.md

@@ -1,57 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, caste, color, religion, or sexual
-identity and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy toward other community members
-
-Examples of unacceptable behavior:
-
-* The use of sexualized language or imagery, and sexual attention or advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at
-**campagno.matheus@gmail.com**.
-
-All complaints will be reviewed and investigated promptly and fairly.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/),
-version 2.1, available at
-[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html).

package/CONTRIBUTING.md

@@ -1,79 +0,0 @@
-# Contributing to Kaelum
-
-Thank you for your interest in contributing to Kaelum! Every contribution helps make the framework better.
-
-## Getting Started
-
-1. **Fork** the repository on GitHub
-2. **Clone** your fork locally:
-   ```bash
-   git clone https://github.com/YOUR_USERNAME/kaelum.git
-   cd kaelum
-   ```
-3. **Install** dependencies:
-   ```bash
-   npm install
-   ```
-4. **Run tests** to make sure everything works:
-   ```bash
-   npm test
-   ```
-
-## Development Workflow
-
-1. Create a new branch from `main`:
-   ```bash
-   git checkout -b feat/your-feature
-   ```
-2. Make your changes
-3. Write or update tests as needed
-4. Run `npm test` to verify
-5. Commit using [Conventional Commits](https://www.conventionalcommits.org/):
-   ```bash
-   git commit -m "feat(core): add new feature"
-   ```
-6. Push and open a Pull Request
-
-## Commit Convention
-
-We follow **Conventional Commits**:
-
-| Prefix | Usage |
-|--------|-------|
-| `feat` | New feature |
-| `fix` | Bug fix |
-| `docs` | Documentation only |
-| `refactor` | Code change that neither fixes a bug nor adds a feature |
-| `test` | Adding or updating tests |
-| `chore` | Maintenance tasks |
-| `perf` | Performance improvements |
-
-## Pull Request Guidelines
-
-- Describe **what** changed and **why**
-- Reference related issues (e.g., `Closes #42`)
-- Keep PRs focused — one feature or fix per PR
-- Ensure all tests pass
-- Update documentation if applicable
-
-## Reporting Bugs
-
-Use the [Bug Report](https://github.com/kaelumjs/kaelum/issues/new?template=bug_report.md) issue template. Include:
-
-- Steps to reproduce
-- Expected vs actual behavior
-- Node.js and Kaelum versions
-- Relevant logs or error messages
-
-## Suggesting Features
-
-Use the [Feature Request](https://github.com/kaelumjs/kaelum/issues/new?template=feature_request.md) issue template. Describe:
-
-- The problem you're trying to solve
-- Your proposed solution
-- Any alternatives you considered
-
-## Code of Conduct
-
-This project follows the [Contributor Covenant Code of Conduct](./CODE_OF_CONDUCT.md).
-By participating, you agree to abide by its terms.

package/SECURITY.md

@@ -1,42 +0,0 @@
-# Security Policy
-
-## Supported Versions
-
-| Version | Supported |
-|---------|-----------|
-| 1.4.x   | ✅ Active  |
-| < 1.4   | ❌ End of life |
-
-## Reporting a Vulnerability
-
-If you discover a security vulnerability, please report it responsibly.
-
-**Do NOT open a public GitHub issue for security vulnerabilities.**
-
-Instead, please email us at: **campagno.matheus@gmail.com**
-
-Include:
-
-- A description of the vulnerability
-- Steps to reproduce the issue
-- Potential impact
-- Suggested fix (if any)
-
-## Response Timeline
-
-- **Acknowledgment**: Within 48 hours
-- **Initial assessment**: Within 1 week
-- **Fix & release**: Depending on severity, typically within 2 weeks
-
-## Disclosure Policy
-
-- We will coordinate with you on disclosure timing
-- We will credit reporters in the release notes (unless you prefer anonymity)
-- We follow [responsible disclosure](https://en.wikipedia.org/wiki/Responsible_disclosure) practices
-
-## Security Best Practices for Users
-
-- Always use the latest version of Kaelum
-- Keep your dependencies up to date (`npm audit`)
-- Never expose `exposeStack: true` in production
-- Use `helmet` via `setConfig({ helmet: true })` for HTTP security headers