Robin Malfait f15cace373
ensure we expect the correct amount of assertions
It is a bit of noise but it will ensure that we don't have false
positives. For example when you have the following code:

```js
it('should fail', () => {
  return promise.catch((err) => {
    expect(err).toBeInstanceOf(Error)
  });
});
```

You would expect that the test passes because we have an expect in the
`.catch` block. However if the promise just resolves it means that no
assertions are executed and the test is considered successful. So in
this case it will _also_ call but for the incorrect reasons!
2020-08-22 00:10:34 +02:00
2020-08-07 15:45:59 -04:00
2020-08-18 08:21:33 -04:00
2019-03-14 15:51:21 -05:00
2020-05-01 15:16:59 -04:00
2020-08-18 08:21:33 -04:00
2019-03-14 15:51:21 -05:00
2019-03-14 15:51:21 -05:00
2017-12-29 22:32:43 +01:00
2020-08-18 13:29:12 -04:00
2020-05-13 12:58:40 +09:00

Tailwind CSS
A utility-first CSS framework for rapidly building custom user interfaces.

Build Status Total Downloads Latest Release License


Documentation

For full documentation, visit tailwindcss.com.

Community

For help, discussion about best practices, or any other conversation that would benefit from being searchable:

Discuss Tailwind CSS on GitHub

For casual chit-chat with others using the framework:

Join the Tailwind CSS Discord Server

Contributing

If you're interested in contributing to Tailwind CSS, please read our contributing docs before submitting a pull request.

Description
A utility-first CSS framework for rapid UI development.
Readme 222 MiB
Languages
JavaScript 90.6%
CSS 7.6%
HTML 1.7%