Skip to content

fix(--require): Resolve project local modules in npx context

Latest
Compare
Choose a tag to compare
@karfau karfau released this 10 Apr 21:08
v0.4.1

When executing a local TypeScript module and using --require=ts-node/register option,
node was trying to resolve it inside the temporary npx folder.
This behaviour doesn't currently make sense, now modules required via this option
are always resolved relative from the current working directory of the script.
This currently prevents requiring a module that only exists in the npx context, but that could be added back easily if needed. #49

https://nodejs.org/docs/latest-v10.x/api/all.html#modules_require_resolve_request_options

All other commits are related to updating dependencies or configuring renovate.
Release notes and hand crafted since npm run release failed when trying to push the tag.
For list of commits see v0.4.0...v0.4.1