Option "resolver" is not considered valid

[suchipi]

Do you want to request a feature or report a bug?
Bug

What is the current behavior?

The "resolver" option is not considered valid, despite its presence in the documentation.

Repro: https://repl.it/G90C
(Just the default https://repl.it/languages/jest with "resolver": "something" added to config)

What is the expected behavior?

resolver should be a valid config option or it should be deprecated/not documented.

[thymikee]

resolver is not officially released yet, it will be in Jest v20.

[thymikee]

Also, @amasad can you please update Jest to v19.0.2 on repl.it?

[amasad]

@thymikee Sure. We're moving to Google Cloud from AWS this week so will probably take until next week before we get it out. (We're also trying to automate updates)

[thymikee]

Yeah awesome! Thank you.

[suchipi]

Thanks for the clarification.

This is the third time I've tried to use an unavailable feature from a newer jest version because I read about it in the docs (first two were toMatchObject and asymmetric matchers). Part of the issue is that CRA is usually a bit behind in Jest version compared to the docs.

Would it be useful to version the API docs, similar to what node does?

[thymikee]

We already do something like that (but with various luck, as you can see 😄): here's corresponding PR #3191.

[JesperWe]

When are you releasing v20? I just started with Jest yesterday, and was completely confused by the docs being ahead of the release, especially since the docs on how to test async stuff has a lot of v20 features in it.

[thymikee]

In 3-4 weeks, after @cpojer returns from his PTO. btw, you can use jest@next to get some features ahead of time. I also encourage you to send a PR with the availability note (like here) if we missed something.

[JesperWe]

Thanks for the tip! I guess @next is built from master then? Any way to tell what commit?

[thymikee]

Unfortunately not. You need to ask @DmitriiAbramov

[JesperWe]

Ah. It announces itself as -- jest@19.1.0-alpha.eed82034 when installing, so there is!

[suchipi]

Is the jest documentation automatically published when commits are made to master? I agree that it's confusing for the docs to be ahead of the release

[thymikee]

cc: @hramos

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.