Esmodule breaks, cljs config extension is recommended but not found

[janat08]

Discussed in #7150

^{Originally posted by janat08 January 21, 2022}
I have package.json that says I’m working on esmodule. I got warning that config extension needs to change after reading docs I believe i must also specify new config location when running jit compilation because none of content is detected. Am I right?

[molenick]

I think I'm having the same issue:

npx tailwindcss build -i demo/tailwind-base.css -o demo/style.css

warn - The `content` option in your Tailwind CSS configuration is missing or empty.
warn - Configure your content sources or your generated CSS will be missing styles.
warn - https://tailwindcss.com/docs/content-configuration

I do have a content tag in tailwind.config.cjs, but when I look at demo/style.css it's missing most of what I expect.

[molenick]

In my project, I was able to get it to build without a config file with this:

npx tailwindcss build -i demo/tailwind-base.css -o demo/style.css --content "./demo/index.html"

It seemed like build wasn't picking up my config with a cjs extension, but specifying the content using --content seems to build as I expect.

[Xeevis]

CLI defaults to ./tailwind.config.js

tailwindcss/src/cli.js

Lines 388 to 392 in ce98735

	let configPath = args['--config']
	? args['--config']
	: ((defaultPath) => (fs.existsSync(defaultPath) ? defaultPath : null))(
	path.resolve('./tailwind.config.js')
	)

There used to be support for detecting cjs, but for some reason that was removed.

Just pass in --config ./tailwind.config.cjs as command argument.

[janat08]

Then this should be included in terminal prompt to rename file

[thecrypticace]

Thanks for opening the issue! In our insiders build we now attempt to detect that you're in an ES module and will create a config file with a .cjs extension in when we do. This also works for the postcss config file when using the -p flag. You can try out insiders build by installing it via npm: npm install tailwindcss@insiders