[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"github-release-nuxt-ui-v4.12.1":3,"$f2v3tzw7dti6zg":-1},{"adjacent":4,"latestReleases":16,"relatedArticles":31,"relatedArticlesAreVersioned":8,"release":40},{"newer":5,"older":11},{"htmlUrl":6,"id":7,"isPrerelease":8,"name":9,"publishedAt":10,"tagName":9},"https:\u002F\u002Fgithub.com\u002Fnuxt\u002Fui\u002Freleases\u002Ftag\u002Fv4.12.2","01a1e43a-b5c1-762e-9c0b-b1a585caa4f0",false,"v4.12.2","2026-11-16T11:16:50.000Z",{"htmlUrl":12,"id":13,"isPrerelease":8,"name":14,"publishedAt":15,"tagName":14},"https:\u002F\u002Fgithub.com\u002Fnuxt\u002Fui\u002Freleases\u002Ftag\u002Fv4.12.0","01a1404a-d686-716a-80d9-c38197502401","v4.12.0","2026-10-15T14:08:12.000Z",[17,18,19,23,27],{"id":7,"isPrerelease":8,"name":9,"publishedAt":10,"tagName":9},{"id":13,"isPrerelease":8,"name":14,"publishedAt":15,"tagName":14},{"id":20,"isPrerelease":8,"name":21,"publishedAt":22,"tagName":21},"01a0f831-ca6d-75a3-b346-cd122695e021","v4.11.3","2026-10-01T13:36:34.000Z",{"id":24,"isPrerelease":8,"name":25,"publishedAt":26,"tagName":25},"01a0c8fc-d675-768f-bc9d-b203b4ef4d1e","v4.11.2","2026-09-22T10:57:12.000Z",{"id":28,"isPrerelease":8,"name":29,"publishedAt":30,"tagName":29},"01a07c99-2835-7139-a2b4-dc1366a91f12","v4.11.1","2026-09-07T12:52:35.000Z",[32],{"id":33,"image":34,"publishedAt":35,"slug":36,"sourceName":37,"summary":38,"title":39},"019ddc9c-805c-71c8-81be-4ae362cfeb7c","https:\u002F\u002Fblog.vueschool.io\u002Fwp-content\u002Fuploads\u002F2026\u002F04\u002Fcollaborative-editor-example.jpg","2026-04-28T00:00:34.000Z","vibe-coding-a-collaborative-editor-with-comment-support-with-nuxt-ui-and-jazz","VueSchool","This article explores the creation of a collaborative editor using Nuxt UI and Jazz, focusing on real-time editing and comment support. It discusses the final product's features, including a rich text editor with a toolbar, image upload capabilities, and a layout optimized for collaboration. The author also shares insights on leveraging AI in the development process.","Vibe Coding a Collaborative Editor with Comment Support with Nuxt UI and Jazz",{"htmlUrl":41,"id":42,"isPrerelease":8,"name":43,"projectId":44,"projectName":45,"projectOwner":46,"projectRepo":47,"projectUrl":48,"publishedAt":49,"summary":50,"tagName":43,"updatedAt":51,"breakingChangesHtml":52,"displayName":53,"hasBreakingChanges":8,"indexable":54,"notesHtml":55,"version":56},"https:\u002F\u002Fgithub.com\u002Fnuxt\u002Fui\u002Freleases\u002Ftag\u002Fv4.12.1","01a1e43a-b5ce-710b-87d6-9585995edb28","v4.12.1","019d75ac-bef8-7578-b1f1-429ff8d0dc0f","Nuxt UI","nuxt","ui","https:\u002F\u002Fgithub.com\u002Fnuxt\u002Fui","2026-11-16T10:34:09.000Z","Nuxt UI v4.12.1 addresses a critical security vulnerability related to untrusted markdown rendering, which could allow code execution on the server. Additionally, it includes bug fixes for component rendering issues and the ContentSearch component to prevent double escaping of result text.","2026-11-16T12:00:21.689Z",null,"Nuxt UI v4.12.1",true,"\u003Ch2>🔒 Security\u003C\u002Fh2>\n\u003Cp>This release fixes \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fnuxt\u002Fui\u002Fsecurity\u002Fadvisories\u002FGHSA-x9jw-j844-v24h\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">GHSA-x9jw-j844-v24h\u003C\u002Fa>, a critical issue where untrusted markdown rendered through Nuxt UI components could run code on the server.\u003C\u002Fp>\n\u003Cp>You&#39;re affected if your app \u003Cstrong>server renders markdown that users or an LLM can write\u003C\u002Fstrong> (chat messages, comments, CMS previews) with \u003Ccode>comark\u003C\u002Fcode>, \u003Ccode>@nuxtjs\u002Fmdc\u003C\u002Fcode> or \u003Ccode>@nuxt\u002Fcontent\u003C\u002Fcode>. Sites that only render their own markdown files aren&#39;t. Update to \u003Ccode>4.12.1\u003C\u002Fcode> even if you already updated \u003Ccode>comark\u003C\u002Fcode> or \u003Ccode>@nuxtjs\u002Fmdc\u003C\u002Fcode>, they don&#39;t cover every case on their own.\u003C\u002Fp>\n\u003Cp>Components no longer render an \u003Ccode>as\u003C\u002Fcode> value or an icon that is a plain object with a \u003Ccode>template\u003C\u002Fcode> string or a forged VNode, and an \u003Ccode>as\u003C\u002Fcode> like \u003Ccode>script\u003C\u002Fcode> or \u003Ccode>iframe\u003C\u002Fcode> falls back to the default element. Passing a \u003Ccode>{ template }\u003C\u002Fcode> component as \u003Ccode>as\u003C\u002Fcode> or as an icon, which only worked with the runtime compiler, now renders the default element instead.\u003C\u002Fp>\n\u003Ch2>🐛 Bug Fixes\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>components:\u003C\u002Fstrong> ignore components compiled from a template string (\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fnuxt\u002Fui\u002Fcommit\u002F7e07a529fe0d7e176ae0deab07835dd66afd39ab\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">7e07a52\u003C\u002Fa>)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>ContentSearch:\u003C\u002Fstrong> stop escaping result text twice (\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fnuxt\u002Fui\u002Fissues\u002F7374\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">#7374\u003C\u002Fa>) (\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fnuxt\u002Fui\u002Fcommit\u002F21ee24361252a5e3100ca52cdcd2c3bebadc9cf4\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">21ee243\u003C\u002Fa>)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>:green_heart: Contributors\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>@benjamincanac\u003C\u002Fli>\n\u003Cli>@onmax\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Full Changelog\u003C\u002Fstrong>: \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fnuxt\u002Fui\u002Fcompare\u002Fv4.12.0...v4.12.1\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">https:\u002F\u002Fgithub.com\u002Fnuxt\u002Fui\u002Fcompare\u002Fv4.12.0...v4.12.1\u003C\u002Fa>\u003C\u002Fp>\n","4.12.1"]