Andreas Lind
Andreas Lind
Jest does use the `vm` module in a bunch of places, so that's probably it: ``` [jest]$ ag vm | grep -P 'require|import' | grep -v __tests__ types/Environment.js:12:import type {Script}...
Good idea. If we consider `expect.it` a "safe" escape, we could even consider it for `to equal`.
jest's `expect` implementation has the concept of a "matcher" (very similar to `expect.it`) that can fix with pretty much any assertion, including `toEqual`: ```js expect({apples: 6, bananas: 3}).toEqual({ apples: expect.toBeWithinRange(1,...
Well, I don't think it'd be easy to implement this, especially not if we want it across every assertion. The "good idea" part was mostly a tip of the hat...
> We already have this functionality with `to exhaustively satisfy` right? Yes!
``` md [](http://npmjs.com/package/{repoName}) ```
The deploy fails everywhere else with: ``` 11:25:18 PM: Build ready to start 11:25:19 PM: build-image version: 84aca9ba39e0ee86ba194760fbfc51a808f62543 11:25:19 PM: buildbot version: 57d44fd1631cc3fff8b38fbaf88d3d04f946418a 11:25:20 PM: Fetching cached dependencies 11:25:20 PM:...
Ah, good idea. I've changed the settings so only the `v11-netlify-deploy-config` branch is built now.
> Implementation wise I think it is very straightforward - one thing I learnt from trying unassessed was that we may may not want to expose all the assertions like...
Hopefully because of the extensibility and quality of the output when an assertion fails? :)