fix: Poor performance with Nuxt-Mapbox & No access to map data (Circular JSON object)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.3k
- Forks
- 214
- Avg merge
- 13h 22m
- Merged PRs (30d)
- 18
Description
🐛 The bug
When using devtools with the Nuxt-Mapbox module causes poor performance once the map is loaded. Data from the map stored with useState is not visible with this error shown in console:
🛠️ To reproduce
https://stackblitz.com/edit/github-mdpukv
🌈 Expected behavior
Expect the same performance with or without devtools, and be able to analyze the mapbox object in the devtools.
ℹ️ Additional context
No response
Contributor guide
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 StackBlitz reproduction using Nuxt-Mapbox and inspect how devtools handles map data stored with useState. Trace the path that reports the circular JSON error and causes poor performance. Done means the map data can be analyzed in devtools without the error and performance remains comparable with devtools disabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxt, typescript
- Domain
- devtools, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100