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

Optional array dedupe for wrangler.toml #2435

Open
oritwoen opened this issue May 11, 2024 · 0 comments
Open

Optional array dedupe for wrangler.toml #2435

oritwoen opened this issue May 11, 2024 · 0 comments

Comments

@oritwoen
Copy link
Contributor

oritwoen commented May 11, 2024

Environment

------------------------------
- Operating System: Linux
- Node Version:     v20.13.0
- Nuxt Version:     3.12.0-28588152.416d76ab
- CLI Version:      3.11.2-1712838256.8df35eb
- Nitro Version:    2.10.0-28585081.346a4950
- Package Manager:  pnpm@9.1.0
- Builder:          -
- User Config:      future, routeRules, app, modules, extends, colorMode, experimental, runtimeConfig, image, devtools, nitro, ui, vueuse, vue, eslint, hub
- Runtime Modules:  @nuxt/ui@2.16.0, @nuxt/fonts@0.7.0, @nuxt/image@1.7.0, @nuxt/eslint@0.3.10, @nuxt/scripts@0.4.0, @vueuse/nuxt@10.9.0, @nuxt/test-utils/module@3.11.0, @nuxthub/core@0.5.14
- Build Modules:    -
------------------------------

Reproduction

Set below config in nuxt.config.ts

nitro: {
    preset: 'cloudflare-pages',
    cloudflare: {
        wrangler: {
            name: 'website',
            compatibility_flags: ['nodejs_compat'],
	},
    }
},

Describe the bug

With each build, an identical flag is added as in the screenshot.

Theoretically, this is not a bug because in case of one-time generation, i.e. the main assumption, it will work correctly in CI.

However, if you want to test several builds locally, you have to delete the wrangler.toml file each time because wrangler pages dev gives the following error:

✘ [ERROR] service core:user:website: Compatibility flag specified multiple times: nodejs_compat

Zrzut ekranu z 2024-05-11 19-58-23

Additional context

No response

Logs

No response

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

1 participant