Faker.js: faker.date.soon is not a function

[embiem]

I'm running faker v4.1.0, and the faker.date.soon() function is missing there.

[embiem]

OK, I just saw that it's actually new in the master branch but has not been released yet.

Sorry for this quick-shot issue. It's rare that the doc's are up-to-date ahead of the release ;-)

[niwrA]

I got the same error in typescript - seems that the types define it but the function is not there yet ... strange. Will continue to investigate.

[kdshop]

stumbled upone same issue but after lecture of this line https://github.com/Marak/faker.js/blob/d3ce6f1a2a9359574e7f31f14d4901648047c45a/lib/date.js#L105 i am confused

[akhoury]

@Konrad008 what's released on npm doesn't have that method date.soon yet

see the release tree, no soon in there
https://github.com/Marak/faker.js/blob/v4.1.0/lib/date.js

@Marak needs to npm publish when ready

__but__, you can install from github if you want to _live on the edge_

in package.json

// or devDependencies

"dependencies": {
     ... 
    "faker": "github:Marak/faker.js#master",
    ... 
}

[asap]

Any ETA on when soon will be released?

[MKRazz]

Hopefully soon.

[eddybrando]

Any real roadmap tho? Because the last npm release was 2 years ago.

Otherwise I'll consider forking master and releasing a parallel updated npm package.

[akhoury]

do it

[hudhaifahz]

A good alternative - use decimal places on the future function:
const dueAt = faker.date.future(0.1,createdAt)

[wgrabowski]

Headless Chrome on Jenkins stuck on this without any error, so this was a big trouble for me, since this was on build verifying PR in Bitbucket. @Marak are you planning to update npm package to fix this error?

[Ricardonacif]

We want that feature :D 💃

[gaspardip]

Just use recent with negative argument.

recent(-1)

[olaven]

The case of @niwrA still holds. 🙁

Is this planned for release soon?
If not, should it be removed from the type definitions?

[DmitryEfimenko]

@Marak, any word on this?

[sujeet-agrahari]

What a wonderful package by careless devs. Issue was created two years ago still not fixed. Kudos to the devs.

[loremaps]

I believe this is resolved after v5.0.0 release and can be closed.