Adjust European short trip heuristic from >3 days to >1 day to correctly detect when user has returned home from European trips. This fixes the April 29-30, 2023 case where the location incorrectly showed "Sankt Georg, Hamburg" instead of "Bristol" when the user was free (no events scheduled) after the foss-north trip ended on April 27. The previous logic required more than 3 days to pass before assuming return home from European countries, but for short European trips by rail/ferry, users typically return within 1-2 days. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> |
||
---|---|---|
.. | ||
index.d.ts | ||
index.js | ||
license | ||
package.json | ||
readme.md |
resolve-from 
Resolve the path of a module like
require.resolve()
but from a given path
Install
$ npm install resolve-from
Usage
const resolveFrom = require('resolve-from');
// There is a file at `./foo/bar.js`
resolveFrom('foo', './bar');
//=> '/Users/sindresorhus/dev/test/foo/bar.js'
API
resolveFrom(fromDirectory, moduleId)
Like require()
, throws when the module can't be found.
resolveFrom.silent(fromDirectory, moduleId)
Returns undefined
instead of throwing when the module can't be found.
fromDirectory
Type: string
Directory to resolve from.
moduleId
Type: string
What you would use in require()
.
Tip
Create a partial using a bound function if you want to resolve from the same fromDirectory
multiple times:
const resolveFromFoo = resolveFrom.bind(null, 'foo');
resolveFromFoo('./bar');
resolveFromFoo('./baz');
Related
- resolve-cwd - Resolve the path of a module from the current working directory
- 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