tailwindcss/tests/defaultTheme.test.js

import theme from '../src/public/default-theme'
import configStub from '../stubs/defaultConfig.stub.js'

test.todo('remove mutation from these tests so we can run against both engines')

test('the default theme matches the stub', () => {
  expect(theme).toEqual(configStub.theme)
})

test('modifying the default theme does not affect the stub', () => {
  theme.colors = {}
  expect(theme).not.toEqual(configStub.theme)
})
Improve public API (#5526) * introduce `public` folder This can contain all of the `public` functions we want to expose. This will be a bit nicer for example when you want to use internal/private functions (we use some in the vscode intellisense plugin). * use public `resolveConfig` function * expose resolveConfig in the root This will use the resolveConfig we expose from the `public` folder. We can probably generate these as well. * make `colors` public * make `default config` public * make `default theme` public * make `create plugin` public * update to public paths * remove `@tailwindcss/aspect-ratio` from tests This should be tested in its own repo instead. * remove `@tailwindcss/aspect-ratio` as a dependency * drop `Build` step from CI The build step is not a prerequisite anymore for running the tests. When we want to release a new (insiders) release, the `prepublishOnly` step will be executed for us. Before this change, it would have been executed twice: - Once before the tests - Once before the actual release * improve paths for caching purposes * add pretest scrip for generating the plugin list Now that we can use `SWC`, automatically generating the plugin list before running the tests is super fast and you don't even have to think about it anymore! 2021-09-26 12:44:13 +02:00			`import theme from '../src/public/default-theme'`
Updated CLI init commend 2019-03-14 15:51:21 -05:00			`import configStub from '../stubs/defaultConfig.stub.js'`

Run test suite against both engines (#10373) * Run test suite against both engines * make eslint happy * only run `stable` tests on Node 12 * use normal expectation instead of snapshot file When we run the tests only against `stable` (for node 12), then the snapshots exists for the `Oxide` build. They are marked as `obsolete` and will cause the `npm run test` script to fail. Sadly. Inlined them for now, but ideally we make those tests more blackbox-y so that we test that we get source maps and that we can map the sourcemap back to the input files (without looking at the actual annotations). * properly indent inline css Co-authored-by: Adam Wathan <4323180+adamwathan@users.noreply.github.com> Co-authored-by: Robin Malfait <malfait.robin@gmail.com> 2023-01-20 12:45:04 -05:00			`test.todo('remove mutation from these tests so we can run against both engines')`

Updated CLI init commend 2019-03-14 15:51:21 -05:00			`test('the default theme matches the stub', () => {`
			`expect(theme).toEqual(configStub.theme)`
			`})`

			`test('modifying the default theme does not affect the stub', () => {`
			`theme.colors = {}`
			`expect(theme).not.toEqual(configStub.theme)`
			`})`