nuxt-modules / nuxt-modules/device
Custom property not saved after being assigned on server side
Open
Nobody has claimed this yet.
3.x
pending triage
- Dominant language
- TypeScript
- Stars
- 1k
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
Description
Reproduction: https://github.com/RomanSkrypnik/nuxt-device-issue
Plugin:
Console:
Result:
Is that an expected behavior or a bug?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked reproduction at https://github.com/RomanSkrypnik/nuxt-device-issue and the server-side plugin configuration shown in the issue. Compare the custom property assignment with the value shown in the console, then determine whether the property should persist after server-side assignment. Done means the expected behavior is documented or the property is retained as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxtjs, typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100