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

Nuxt Build Error (RegExp.prototype.exec) #27012

Open
SossenSystems opened this issue May 1, 2024 · 3 comments
Open

Nuxt Build Error (RegExp.prototype.exec) #27012

SossenSystems opened this issue May 1, 2024 · 3 comments

Comments

@SossenSystems
Copy link

Environment

------------------------------
- Operating System: Darwin
- Node Version:     v20.11.0
- Nuxt Version:     3.11.2
- CLI Version:      3.11.1
- Nitro Version:    2.8.1
- Package Manager:  npm@9.6.6
- Builder:          -
- User Config:      devtools, modules, css, app, router, auth, devServer, robots, colorMode, pinia, build, typescript, piniaPersistedstate, hooks, site, sitemap, nitro, runtimeConfig, features
- Runtime Modules:  nuxt-icon@0.6.10, @nuxtjs/google-fonts@3.2.0, @formkit/auto-animate/nuxt@0.8.2, @pinia/nuxt@0.5.1, @pinia-plugin-persistedstate/nuxt@1.2.0, @nuxt/image@1.6.0, @nuxt/ui@2.15.2, @vueuse/nuxt@10.9.0, v-wave/nuxt, @sidebase/nuxt-auth@0.7.2, @nuxtjs/seo@2.0.0-rc.10, nuxt-aos@1.2.4
- Build Modules:    -
------------------------------

Reproduction

Describe the bug

 ERROR  x Build failed in 886ms                                                                                                                            2:08:15 AM


 ERROR  Nuxt Build Error: [vite:css] [postcss] Method RegExp.prototype.exec called on incompatible receiver [object RegExp]                                2:08:15 AM
file: /Users/mynuxtproject/node_modules/tailwindcss/tailwind.css:undefined:NaN

  file: node_modules/tailwindcss/tailwind.css:undefined:NaN
  at Proxy.exec (<anonymous>)
  at Proxy.test (<anonymous>)
  at registerPlugins (node_modules/tailwindcss/lib/lib/setupContextUtils.js:899:38)
  at createContext (node_modules/tailwindcss/lib/lib/setupContextUtils.js:1221:5)
  at getContext (node_modules/tailwindcss/lib/lib/setupContextUtils.js:1278:19)
  at node_modules/tailwindcss/lib/lib/setupTrackingContext.js:118:81
  at node_modules/tailwindcss/lib/processTailwindFeatures.js:46:11
  at plugins (node_modules/tailwindcss/lib/plugin.js:38:69)
  at LazyResult.runOnRoot (node_modules/postcss/lib/lazy-result.js:329:16)
  at LazyResult.runAsync (node_modules/postcss/lib/lazy-result.js:258:26)

and

 ERROR  x Build failed in 1.95s                                                                                                                                      2:03:45 AM


 ERROR  Nuxt Build Error: [vite:css] [postcss] Method RegExp.prototype.exec called on incompatible receiver [object RegExp]                                          2:03:45 AM
file: /project_live/node_modules/.cache/nuxt-google-fonts/css/nuxt-google-fonts.css:undefined:NaN

  file: node_modules/.cache/nuxt-google-fonts/css/nuxt-google-fonts.css:undefined:NaN
  at Proxy.exec (<anonymous>)
  at Proxy.test (<anonymous>)
  at registerPlugins (node_modules/tailwindcss/lib/lib/setupContextUtils.js:899:38)
  at createContext (node_modules/tailwindcss/lib/lib/setupContextUtils.js:1221:5)
  at getContext (node_modules/tailwindcss/lib/lib/setupContextUtils.js:1278:19)
  at node_modules/tailwindcss/lib/lib/setupTrackingContext.js:118:81
  at node_modules/tailwindcss/lib/processTailwindFeatures.js:46:11
  at plugins (node_modules/tailwindcss/lib/plugin.js:38:69)
  at LazyResult.runOnRoot (node_modules/postcss/lib/lazy-result.js:329:16)
  at LazyResult.runAsync (node_modules/postcss/lib/lazy-result.js:258:26)

Additional context

Get this error after "nuxt build"

Logs

No response

Copy link
Contributor

github-actions bot commented May 1, 2024

Would you be able to provide a reproduction? 🙏

More info

Why do I need to provide a reproduction?

Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making.

What will happen?

If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritize it based on its severity and how many people we think it might affect.

If needs reproduction labeled issues don't receive any substantial activity (e.g., new comments featuring a reproduction link), we'll close them. That's not because we don't care! At any point, feel free to comment with a reproduction and we'll reopen it.

How can I create a reproduction?

We have a couple of templates for starting with a minimal reproduction:

👉 https://stackblitz.com/github/nuxt/starter/tree/v3-stackblitz
👉 https://codesandbox.io/s/github/nuxt/starter/v3-codesandbox

A public GitHub repository is also perfect. 👌

Please ensure that the reproduction is as minimal as possible. See more details in our guide.

You might also find these other articles interesting and/or helpful:

@danielroe danielroe added the upstream label May 1, 2024 — with Volta.net
@SossenSystems
Copy link
Author

Sure, here is the reproduction: https://stackblitz.com/edit/github-wvkjrt

@manniL
Copy link
Member

manniL commented May 2, 2024

@SossenSystems Posting your whole project is no "minimal" reproduction.

Please ensure that the reproduction is as minimal as possible. See more details in our guide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants