Bernt
58ca4e68db
- Go backend API with full CRUD for all modules (CRM, Sales, Finance, HR, Legal, Marketing, Support, Purchase, Inventory, Projects, Automation, Analytics) - Rust analytics service with parallel report generation - C runtime with POSIX shared memory IPC - PostgreSQL schema with 30+ tables, full migrations - Redis cache, sessions, pub/sub - Kafka event streaming with Zookeeper - WebSocket hub for real-time updates - Automation engine with cron jobs, workflows, event triggers - JWT authentication, multi-tenant from start - Docker Compose with all services - Nginx reverse proxy with rate limiting - Integration tests passing - Feature gap analysis against Fortnox/Odoo/Visma Refs: BOC-001
resolve-cwd 
Resolve the path of a module like
require.resolve()but from the current working directory
Install
$ npm install resolve-cwd
Usage
const resolveCwd = require('resolve-cwd');
console.log(__dirname);
//=> '/Users/sindresorhus/rainbow'
console.log(process.cwd());
//=> '/Users/sindresorhus/unicorn'
console.log(resolveCwd('./foo'));
//=> '/Users/sindresorhus/unicorn/foo.js'
API
resolveCwd(moduleId)
Like require(), throws when the module can't be found.
resolveCwd.silent(moduleId)
Returns undefined instead of throwing when the module can't be found.
moduleId
Type: string
What you would use in require().
Related
- resolve-from - Resolve the path of a module from a given path
- import-from - Import a module from a given path
- import-cwd - Import a module from the current working directory
- resolve-pkg - Resolve the path of a package regardless of it having an entry point
- import-lazy - Import a module lazily
- resolve-global - Resolve the path of a globally installed module
License
MIT © Sindre Sorhus