Switch Documentation to npm and Streamline Build Scripts
This release focuses on modernizing the documentation project's dependency management and aligning build processes with the broader Fjell ecosystem direction. The main goal is to standardize on npm for documentation tooling, simplify CI/CD workflows, and update dependencies to maintain compatibility and ease of maintenance.
Improvements
- Migrated the documentation project from pnpm to npm:
- Removed
docs/pnpm-lock.yaml - Added
docs/package-lock.jsonto enable npm as the default package manager for the docs
- Removed
- Updated documentation-related scripts (
docs:dev,docs:build,docs:preview,docs:test) in the mainpackage.jsonand withindocs/package.jsonto use npm commands - Updated the
copy-docsscript to utilizenpx copy-docsfor better compatibility and maintainability - Revised the docs GitHub Actions workflow by removing unnecessary explicit
pnpm/npm installsteps—now, the workflow relies on previously installed dependencies and simply runs the docs build script - Simplified custom file copying logic and config:
- Updated
docs.config.tsto import the typedDocsConfigfrom@fjell/docs-template - Removed manual file copy rules for
README.mdandpackage.jsonthat are now handled automatically or in the template/workflow
- Updated
- Upgraded documentation dependencies:
- Bumped
@fjell/docs-templateindocs/package.jsonfrom1.0.5to1.0.17
- Bumped
Dependency Updates
- Main project
@fjell/loggingdependency updated to^4.4.25for improved compatibility across the Fjell ecosystem (no source code changes)
Notes to Developers
- All documentation-related development and CI should now use npm
- No changes to HTTP API source code or runtime behavior—these updates are focused entirely on tooling and documentation infrastructure
- Consistent dependency versions and package management streamline future updates and troubleshooting across environments.