c03f9ad600
* 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! |
||
|---|---|---|
| .. | ||
| collapseAdjacentRules.js | ||
| detectNesting.js | ||
| evaluateTailwindFunctions.js | ||
| expandApplyAtRules.js | ||
| expandTailwindAtRules.js | ||
| generateRules.js | ||
| getModuleDependencies.js | ||
| normalizeTailwindDirectives.js | ||
| resolveDefaultsAtRules.js | ||
| setupContextUtils.js | ||
| setupTrackingContext.js | ||
| setupWatchingContext.js | ||
| sharedState.js | ||
| substituteScreenAtRules.js | ||