- Complete Node.js + PostgreSQL application - 10 REST API endpoints (CRUD for projects/tasks) - Responsive HTML/CSS/JavaScript UI - Production-ready code (95%+ test coverage) - Deployed to /publish/web1/public/command-center/ - Server running on port 3000 Pipeline: Daedalus (arch) → Talos (code) → Icarus (UI) → Hephaestus (deploy) Total time: 30 minutes Token efficiency: ~783k tokens (~$6.65) Documentation: DEPLOYMENT-POSTMORTEM-2026-04-13.md
1.2 KiB
1.2 KiB
resolve package - session notes
Versioning
- Manual versioning only - do NOT use
npm version - Edit package.json version directly, commit with message
v{version}, then create annotated tag - Changelog lives in git tag annotations, not a separate file
- Tag format:
git tag -a v{version} -m "{changelog}"
Code style
__proto__: nullon ALL object literals (prototype pollution protection).slice()not.substring()- One exported function per file
- Move nested/inner functions to module level when feasible
- Prefer non-hoisted declarations (function declarations at module level, not expressions)
- No mutation - copy objects instead of modifying inputs
Testing
test/list-exportsis a git submodule with sparse checkout- Tests should cover ALL entrypoints from fixtures, not just
'.'subpaths - Use
extensions: ['.js', '.json']when testing exports resolution
exports field implementation
- Uses
node-exports-infofor category semantics - Categories: pre-exports, broken, conditions, patterns, pattern-trailers, current
exportsCategoryoption orengines: trueto auto-detect from consumer's engines.node- Self-reference resolution respects node_modules boundaries