Having support for "workdays" would be awesome, to skip the weekends. We can use this to trigger deadlines, without taking the weekends into account.

agenda.schedule('3 workdays');

like "monthly"
"weekly"
etc :)

I know this package is really low maintenance but what do you think about moving this under Agenda org? Since that package quite heavily relies on this, it would be good to have push rights among same devs.

instead of calling days gitlab api uses "d"
example

human_time = 1d

and I want convert that 1d to timestamp so I can use datefns to add to other date or something like that, can I do that? does it recognize if write d instead of days?

Hello @rschmukler ,

To support more word numbers, instead of adding more data, we could use something like node-numbered to do this and remove some code from the project while extending it's support. Would you be accepting such contribution? What do you think?

I suppose, to use that there needs to be a little bit of refactoring on how the code works. I'm thinking we could instead use the following algorithm:

1. Find the units in the string and split the string using them.
2. Pass the remaining strings to node-numbered which will convert them to numbers.
3. Process it and calculate the total.

Now that Agenda is TypeScript, we should export types directly from human-interval.

👋 @paulmelnikow because you've written Types for this previously at https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/human-interval ;-)

Can you pass the days of the week with the time?

Example:

Wednesday at 10:12AM

when working with agenda I ran into the following issue:

// works perfectly fine
agneda.every('90 seconds')
agenda.every('1.5 minutes')
agenda.every('1 minute and 30 seconds')

// works perfectly fine
agenda.schedule('in 90 seconds')

// does not work
// no error is thrown, the time saved in the database is incorrect though
agenda.schedule('in 1.5 minutes')
agenda.schedule('in 1 minute and 30 seconds')

I am not sure whether this is an rather a missing feature than a bug, it's definitely not expected, unintuitive

thanks a lot @rschmukler for your work on agenda and human-interval - it is an pleasure to use!

I recently cloned the repo, made some changes and tried to run the tests locally using the test script in package.json.

When I ran the test using npm run test locally, it gave me an error
. import should occur before import of ava import/order

Hence I changed the order of the import statements in test.js (Moved import off ava below import of .)

But when I submitted a PR, the travis-ci build failed stating the reason -
ava import should occur before import of .

Is there something we can do to make this uniform? Or am I missing something here?

If I enter everyday as an interval in agenda, it schedules jobs every second.
Similar behavior is not seen with every day.
Not sure if I am doing something wrong here.

For config files it could be useful to have support for inputs like '10s' (for '10 seconds').

Currently it returns a TypeError: Cannot read property '1' of null.

e.g.

humanInterval(60 * 1000); // returns "one minute"

@agenda/maintainers

Is there much point in holding back with things like const and arrow function if we can live without them then we should try and make this work for all browsers if not I'd say we ditch first hand browser support and expect the user to bundle it.

It's useful that the numbers can be localized, however it would also be important to support localizing the names of the units and the separators.

Hello!

@rschmukler could you please add me to NPM for this package so that I could publish new versions? :-) Thanks!