Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tailwind 4.2.1 -> 5.1.3 = FATAL Invalid host defined options #497

Closed
sebalaini opened this issue Jul 9, 2022 · 7 comments
Closed

Tailwind 4.2.1 -> 5.1.3 = FATAL Invalid host defined options #497

sebalaini opened this issue Jul 9, 2022 · 7 comments
Labels
bug Something isn't working

Comments

@sebalaini
Copy link

sebalaini commented Jul 9, 2022

Version

@nuxtjs/tailwindcss: 5.1.3
nuxt: 2.15.8
node: 16.13

Reproduction Link

Steps to reproduce

When upgrading from V4 to V5 there is a fatal error Invalid host defined options
image

I've done this upgrade on another project with yarn and I didn't have any issue but with npm I have this.

These are all my dependencies

  "dependencies": {
    "@nuxt/babel-preset-app": "^2.15.8",
    "@nuxtjs/axios": "^5.13.6",
    "core-js": "^3.23.4",
    "js-cookie": "^3.0.1",
    "nuxt": "^2.15.8",
    "nuxt-fontawesome": "^0.4.0",
    "vuedraggable": "^2.24.3"
  },
  "devDependencies": {
    "@babel/eslint-parser": "^7.18.2",
    "@fortawesome/fontawesome-svg-core": "^6.1.1",
    "@fortawesome/free-regular-svg-icons": "^6.1.1",
    "@fortawesome/free-solid-svg-icons": "^6.1.1",
    "@fortawesome/vue-fontawesome": "^2.0.8",
    "@nuxtjs/dotenv": "^1.4.1",
    "@nuxtjs/eslint-config": "^10.0.0",
    "@nuxtjs/eslint-module": "^3.1.0",
    "@nuxtjs/storybook": "^4.3.2",
    "@nuxtjs/style-resources": "^1.2.1",
    "@nuxtjs/tailwindcss": "^4.2.1",
    "@vue/test-utils": "^1.2.2",
    "babel-core": "7.0.0-bridge.0",
    "eslint": "^8.19.0",
    "eslint-plugin-nuxt": "^3.2.0",
    "jest": "26.6.3",
    "plop": "^3.1.1",
    "postcss": "^8.4.14",
    "postcss-html": "^1.5.0",
    "sass": "^1.53.0",
    "sass-loader": "10.1.1",
    "style-loader": "^3.3.1",
    "stylelint": "^14.9.1",
    "stylelint-config-recommended": "^8.0.0",
    "stylelint-config-standard-scss": "^4.0.0",
    "stylelint-declaration-strict-value": "^1.8.0",
    "vue-jest": "^3.0.7",
    "vue-loader": "15.9.8",
    "webpack": "4.46.0"
  }

What is Expected?

What is actually happening?

@sebalaini sebalaini added the bug Something isn't working label Jul 9, 2022
@othy54
Copy link

othy54 commented Aug 3, 2022

Same here with 5.3.1 :/

@taksugit
Copy link

taksugit commented Aug 26, 2022

This is similar to this(nuxt/bridge#266 (comment))

It does work by adding DISABLE_V8_COMPILE_CACHE=true
However it doesn't work by recreating yarn.lock 😕

@em-piguet
Copy link

rebuilding after removing "node_modules" + yarn.lock + .nuxt/ works for me with "@nuxtjs/tailwindcss": "^5.3.2",

@sebalaini
Copy link
Author

I finally switched to yarn and deleted .nuxt + nod_modules and seems to work now, though a lot of styles seem to be broken even though I don't use deprecated classes 🤷‍♂️

@derHodrig
Copy link

derHodrig commented Dec 1, 2022

Does anyone know how this issue works, when it comes? Im on v6.1.3 and nuxt v2.15.8 and the problem came back. (using default settings)

@aliwesome
Copy link

@derHodrig did you fix this issue?

@derHodrig
Copy link

@aliwesome currently I use nuxt 2.16.3 and nuxt/tailwind 6.6.6 with YARN2 nodelinker and currently I have no issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants