6d40b6a6ca
<!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> When we generate a Next.js application with tailwindcss running with `--turbo` fails due to how the globs are defined inside `tailwind.config.js`. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> Relative paths a singular globs are required with this change tailwind should work with HMR using `--turbo` ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #29946
40 lines
1.6 KiB
TypeScript
40 lines
1.6 KiB
TypeScript
import { createGlobPatternsForDependencies as jsGenerateGlobs } from '@nx/js/src/utils/generate-globs';
|
|
import { relative } from 'path';
|
|
|
|
/**
|
|
* Generates a set of glob patterns based off the source root of the app and its dependencies
|
|
* @param dirPath workspace relative directory path that will be used to infer the parent project and dependencies
|
|
* @param fileGlobPattern pass a custom glob pattern to be used
|
|
*/
|
|
export function createGlobPatternsForDependencies(
|
|
dirPath: string,
|
|
fileGlobPatternToInclude: string = '/**/*.{tsx,ts,jsx,js,html}',
|
|
fileGlobPatternToExclude: string = '/**/*.{stories,spec}.{tsx,ts,jsx,js,html}'
|
|
) {
|
|
try {
|
|
return [
|
|
...jsGenerateGlobs(dirPath, fileGlobPatternToInclude).map((glob) =>
|
|
relative(dirPath, glob)
|
|
),
|
|
...jsGenerateGlobs(dirPath, fileGlobPatternToExclude).map(
|
|
(glob) => `!${relative(dirPath, glob)}`
|
|
),
|
|
];
|
|
} catch (e) {
|
|
/**
|
|
* It should not be possible to reach this point when the utility is invoked as part of the normal
|
|
* lifecycle of Nx executors. However, other tooling, such as the VSCode Tailwind IntelliSense plugin
|
|
* or JetBrains editors such as WebStorm, may execute the tailwind.config.js file in order to provide
|
|
* autocomplete features, for example.
|
|
*
|
|
* In order to best support that use-case, we therefore do not hard error when the ProjectGraph is
|
|
* fundamently unavailable in this tailwind-specific context.
|
|
*/
|
|
console.warn(
|
|
'\nWARNING: There was an error creating glob patterns, returning an empty array\n' +
|
|
`${e.message}\n`
|
|
);
|
|
return [];
|
|
}
|
|
}
|