TypeError: input.includes is not a function
See original GitHub issueVersion
@nuxtjs/tailwindcss: 5.3.0 nuxt: 2.15.8
My Tailwind config
/** @type {import('tailwindcss').Config} */ module.exports = { content: [ "./components/**/*.{js,vue}", "./layouts/**/*.vue", "./pages/**/*.vue", "./plugins/**/*.js", "./nuxt.config.js", ], theme: { extend: {}, }, plugins: [ require('@tailwindcss/forms') ], }
Steps to reproduce
Iโve been using version 5.1.3 without any issues, but the moment I upgraded to 5.2.0 and now also 5.3.0 then, I get the error: TypeError: input.includes is not a function
Version 5.1.3 still works perfectly.
Here are the full error logs: $ nuxt โน Using default Tailwind CSS file from runtime/tailwind.css nuxt:tailwindcss
FATAL input.includes is not a function
at normalizeWindowsPath (node_modules/pathe/dist/index.mjs:2:14) at normalize (node_modules/pathe/dist/index.mjs:17:10) at resolvePath (node_modules/@nuxt/kit/dist/index.mjs:340:10) at node_modules/@nuxtjs/tailwindcss/dist/module.mjs:166:75 at Array.map (<anonymous>) at setup (node_modules/@nuxtjs/tailwindcss/dist/module.mjs:166:64) at async ModuleContainer.normalizedModule (node_modules/@nuxt/kit/dist/index.mjs:607:5) at async ModuleContainer.addModule (node_modules/@nuxt/core/dist/core.js:239:20) at async ModuleContainer.ready (node_modules/@nuxt/core/dist/core.js:51:7) at async Nuxt._init (node_modules/@nuxt/core/dist/core.js:478:5)
โญโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ โ โ โ โ Nuxt Fatal Error โ โ โ โ TypeError: input.includes is not a function โ โ โ โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
error Command failed with exit code 1.
Issue Analytics
- State:
- Created a year ago
- Reactions:4
- Comments:5 (1 by maintainers)
Top GitHub Comments
@phillipstemann btw you should also print out the line
and see for yourself what is wrong, for me somehow nuxt-highlightjs injected an object instead of a string in the css array, and an object is not normalizable for the path and thatโs why it errored out.
@pencilcheck @phillipstemann This should be fixed in the new version 6.1.3. Issue, pull request