michangarrito/apps/backend/node_modules/resolve-cwd
rckrdmrd 97f407c661 [MIGRATION-V2] feat: Migrar michangarrito a estructura v2
- Prefijo v2: MCH
- TRACEABILITY-MASTER.yml creado
- Listo para integracion como submodulo

Workspace: v2.0.0 | SIMCO: v4.0.0
2026-01-10 11:28:54 -06:00
..
node_modules/resolve-from [MIGRATION-V2] feat: Migrar michangarrito a estructura v2 2026-01-10 11:28:54 -06:00
index.d.ts [MIGRATION-V2] feat: Migrar michangarrito a estructura v2 2026-01-10 11:28:54 -06:00
index.js [MIGRATION-V2] feat: Migrar michangarrito a estructura v2 2026-01-10 11:28:54 -06:00
license [MIGRATION-V2] feat: Migrar michangarrito a estructura v2 2026-01-10 11:28:54 -06:00
package.json [MIGRATION-V2] feat: Migrar michangarrito a estructura v2 2026-01-10 11:28:54 -06:00
readme.md [MIGRATION-V2] feat: Migrar michangarrito a estructura v2 2026-01-10 11:28:54 -06:00

resolve-cwd Build Status

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().

  • 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