tailwindcss/integrations/syntax.js

// Small helper to allow for css, html and JavaScript highlighting / formatting in most editors.
module.exports = { css: String.raw, html: String.raw, javascript: String.raw }
Integrations setup (#4354) * add integration test tools * setup jest in the integrations folder * add `test:integrations` script The default `npm test` script will ignore all the tests in the `integrations` folder. * add integration tests with `webpack 5` * add integration tests with `postcss-cli` * add `npm run install:integrations` script This script will run `npm install` in every integration, and in the integrations folder itself (to setup Jest for example). * add `toIncludeCss` custom matcher * increate Jest timeout for integration tests * add integration tests with `vite` * add integration tests with `webpack 4` * add isomorphic fetch * add the ability to wait for specific stdout/stderr output * write vite tests, assert using API calls We will wait for the correct stdout/stderr output, once we know that we can request the fresh css, we will fetch it and make assertions accordingly. Port is currently hardcoded, maybe we should use a packaage to ensure that we use a free port. * add integration tests with `rollup` * add integration tests with `parcel` * run all integration tests in band * add .gitignore in integrations folder 2021-05-18 17:21:35 +02:00			`// Small helper to allow for css, html and JavaScript highlighting / formatting in most editors.`
Improve css expectations in tests (#5819) * use String.raw for css escapes This will allow us to write code like: ```css .mobile\:font-bold {} ``` Instead of ```css .mobile\\:font-bold {} ``` Which resembles "real" css way better in our tests. * use String.raw in integration tests as well 2021-10-18 12:08:48 +02:00			`module.exports = { css: String.raw, html: String.raw, javascript: String.raw }`