Nuxt•2w ago

Readonly mutation in OpnForm works in Docker but not locally

I’m running into a weird issue and I’m trying to understand why it behaves differently in Docker vs local.

Setup:

Nuxt ^3.17.1, Vue ^3.5.13
Works fine when running via Docker
Broken when running locally with
```
npm run dev
```
npm run dev
```
npm run dev
```
npm run dev
or
```
node .output/server/index.mjs
```
node .output/server/index.mjs
```
node .output/server/index.mjs
```
node .output/server/index.mjs

When editing an existing form field in a form builder UI:
In dev mode I get:

[Vue warn] Set operation on key "name" failed: target is readonly

[Vue warn] Set operation on key "name" failed: target is readonly

[Vue warn] Set operation on key "name" failed: target is readonly

[Vue warn] Set operation on key "name" failed: target is readonly

The field value does not update

BUT: if I add a new input field first, I can then edit the name of an existing field just fine

No network errors, no console errors besides the Vue warn.

I need it to run without docker, because the server it will be running on doesn't have docker and we don't have permission to install it.

kapa.ai•12/16/25, 7:37 AM

Hi @Justin. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

kapa.ai•12/16/25, 7:37 AM

----------------------
There’s nothing in the provided knowledge sources that specifically explains a “Set operation on key X failed: target is readonly” warning that behaves differently in Docker vs local for a Nuxt 3 + Vue 3.5.13 app, nor anything about OpnForm or a similar form‑builder pattern.

The closest related items in the sources are:

A memory‑leak issue tied to certain Vue versions, recommending pinning Vue to 3.5.133.5.13. [Memory leak]
General advice about hydration issues and global state changes during SSR, but not about readonly mutations. [SSR/global state]
General Vue reactivity pitfalls (losing reactivity when destructuring/using refs) but no readonly‑proxy behavior differences between environments. [Avoid losing reactivity]

None of the sources mention:

Different readonly/reactive behavior between Docker and non‑Docker runs,
OpnForm or form‑builder‑style code patterns that would cause target is readonlytarget is readonly only in local,
A Nuxt/ Nitro / Vite config flag that would account for this specific discrepancy.

Because of that, I can’t confidently say what is causing your issue based on the available material. The knowledge sources simply don’t contain enough detail to explain:

Why the same code would mutate readonly state locally but not in Docker,
Why adding a new field would temporarily “fix” the ability to edit an existing field.

To move forward, you’d likely need to:

kapa.ai•12/16/25, 7:37 AM

Compare the exact dependency versions (Nuxt, Vue, Vue reactivity runtime, any form libraries) between your Docker image and your local environment.
Inspect where the field data comes from (e.g., props, Pinia store, computed from readonly state) to see if you’re accidentally mutating something that Vue wraps in a readonly proxy—this is the usual cause of that warning, but again, the concrete pattern isn’t described in the sources.

If you can share a minimal repro similar to the StackBlitz links in the issues above, the Nuxt team / community would be able to investigate, but that kind of repro and analysis is not present in the current knowledge set.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

kapa.ai•12/16/25, 7:37 AM

@852960326990430215 Kapa.ai is still learning and improving, please let me know how I did by reacting below.

Readonly mutation in OpnForm works in Docker but not locally

Similar Threads

Similar Threads

Similar Threads