2013 icons are the absolute legends! Everything else isn't even close to that masterpiece.
October 2, 2025 at 4:44 AM
2013 icons are the absolute legends! Everything else isn't even close to that masterpiece.
Amazing news! Following and looking forward to @vuejs.org adapter.
July 17, 2025 at 3:11 AM
Amazing news! Following and looking forward to @vuejs.org adapter.
I contributed to happy-dom before and had great experience. Maybe it went under David's radar 🤷♂️
June 20, 2025 at 7:29 PM
I contributed to happy-dom before and had great experience. Maybe it went under David's radar 🤷♂️
Last time I was amazed this much by it when I realized you can search for objects in videos. And not only it finds videos which contain the object but also shows time range when such object appears in it.
June 7, 2025 at 3:38 PM
Last time I was amazed this much by it when I realized you can search for objects in videos. And not only it finds videos which contain the object but also shows time range when such object appears in it.
Amount of features you out of the box is mind blowing.
May 22, 2025 at 8:34 PM
Amount of features you out of the box is mind blowing.
Thank you! Glad you found it useful!
May 21, 2025 at 5:28 PM
Thank you! Glad you found it useful!
Thanks! New `message` method is something I've been looking forward to.
May 7, 2025 at 7:01 PM
Thanks! New `message` method is something I've been looking forward to.
paulau.dev/blog/ wrote few things about vue, vite and tanstack query
May 6, 2025 at 9:45 PM
paulau.dev/blog/ wrote few things about vue, vite and tanstack query
Have you considered reducing the amount of packages in general?
Single package per framework with all extensions, maybe `@tiptap/pm`, and one more for all pro extensions. Let bundlers do their work. And do major releases more often. I really wonder if this is the path forward with v3 and further.
Single package per framework with all extensions, maybe `@tiptap/pm`, and one more for all pro extensions. Let bundlers do their work. And do major releases more often. I really wonder if this is the path forward with v3 and further.
[Suggestion]: Add common packages (extensions) to the core package · Issue #4837 · ueberdosis/tiptap
Which packages did you experience the bug in? core, extension-* What Tiptap version are you using? 2.1.16 What’s the bug you are facing? I'm always frustrated when I want to add functionality to th...
github.com
December 31, 2024 at 9:50 PM
Have you considered reducing the amount of packages in general?
Single package per framework with all extensions, maybe `@tiptap/pm`, and one more for all pro extensions. Let bundlers do their work. And do major releases more often. I really wonder if this is the path forward with v3 and further.
Single package per framework with all extensions, maybe `@tiptap/pm`, and one more for all pro extensions. Let bundlers do their work. And do major releases more often. I really wonder if this is the path forward with v3 and further.
Also before `@tiptap/pm`, "multiple versions were loaded" issue was (and still is) the most upvoted issue in tiptap repo.
For instance, CodeMirror doesn't sync their versions and single package upgrade regularly breaks typescript types compatibility for us with yarn.
For instance, CodeMirror doesn't sync their versions and single package upgrade regularly breaks typescript types compatibility for us with yarn.
Error: Looks like multiple versions of prosemirror-model were loaded · Issue #577 · ueberdosis/tiptap
Describe the bug When using the editor (e.g. using ENTER key) it's not working, and we got error in the console: Can not convert <> to a Fragment (looks like multiple versions of prosemirror-model ...
github.com
December 31, 2024 at 9:50 PM
Also before `@tiptap/pm`, "multiple versions were loaded" issue was (and still is) the most upvoted issue in tiptap repo.
For instance, CodeMirror doesn't sync their versions and single package upgrade regularly breaks typescript types compatibility for us with yarn.
For instance, CodeMirror doesn't sync their versions and single package upgrade regularly breaks typescript types compatibility for us with yarn.
I voted in favor of keeping versions synced. "Makes it clear which packages are compatible" was my point. I fully understand that you guys would like to ship breaking changes more often. But version syncing just makes it so much simpler for consumers.
December 31, 2024 at 9:50 PM
I voted in favor of keeping versions synced. "Makes it clear which packages are compatible" was my point. I fully understand that you guys would like to ship breaking changes more often. But version syncing just makes it so much simpler for consumers.
TIL?! I always wondered if `import * as v from 'valibot'` and unused schema declarations are fully tree-shakable. And I was absolutely sure it was because of `"sideEffects": false` in valibot's package.json.
Is this not respected by the bundlers? I'm confused.
Is this not respected by the bundlers? I'm confused.
December 24, 2024 at 7:28 PM
TIL?! I always wondered if `import * as v from 'valibot'` and unused schema declarations are fully tree-shakable. And I was absolutely sure it was because of `"sideEffects": false` in valibot's package.json.
Is this not respected by the bundlers? I'm confused.
Is this not respected by the bundlers? I'm confused.
@valibot.dev is just amazing. Thank you for making it!
December 13, 2024 at 4:19 AM
@valibot.dev is just amazing. Thank you for making it!
Reposted by Raman
