`unbuild` migrate

[sxzz]

• write a migration script like tsup (see src/migrate.ts)
• documentation of migration guide, similar to https://tsdown.dev/guide/migrate-from-tsup

[CodeMan62]

can you provide a brief so i can see if I can work on it

[sxzz]

updated

[CodeMan62]

i will take this issue

[pi0]

For reference, unjs/obuild is the official unjs/unbuild replacement based on rolldown by the same author (me). related discussion.

Either tsdown is trying to "feature match" with unbuild (which deserves at least credit then) or if the goal of rolldown is to not be identical but take a different approach, there should really not be "migration" but fairly you could link users to unbuild/obuild as true alternatives. (and we can try to see how to reduce differences)

[sxzz]

I believe we made things clear a few days ago—obuild can use tsdown as a dependency, right? unjs/obuild#24 (comment)

Given the current state of obuild’s implementation, especially since you’ve noted “Features are incomplete” in the README (https://github.com/unjs/obuild#proof-of-concept), obuild can’t fully replace all of unbuild’s features at this point, correct? So for users who need faster performance, tsdown is indeed a migration option worth considering.

[pi0]

I believe we made things clear a few days ago—obuild can use tsdown as a dependency, right?

Yes, I reached out to you in good faith and even considered using tsdown as the underlying library if there are benefits of dedup work (it costs adding more layers of complexity if we do). But not to replace/migrate from unbuild to tsdown!!!

Given the current state of obuild’s implementation,

Please let's be clear, rolldown itself is very unstable and changing rapidly, and tsdown inherits it by nature currently.

obuild can’t fully replace all of unbuild’s features at this point, correct? So, for users who need faster performance, tsdown is indeed a migration option worth considering.

For users who need faster package build times and other unique rolldown features like fewer deps, there is obuild.

Interestingly, you even said you would use obuild for some personal projects if I remember correctly.

This "migration from unbuild" issue at least sounds very hostile not not in good faith towards collaboration.

[sxzz]

Please let's be clear, rolldown itself is very unstable and changing rapidly, and tsdown inherits it by nature currently.

Rolldown’s core functionality is already stable enough at this point. What I meant is that certain features are still missing in obuild—for example, CJS support is explicitly not going to be implemented in obuild, and there are several other features currently absent as well. I’m sure you’re even more aware of this than I am.

For users who need faster package build times and other unique rolldown features like fewer deps, there is obuild

How to migrate for users currently relying on CJS?

Interestingly, you even said you would use obuild for some personal projects if I remember correctly.

There’s no doubt that I said, I would even consider using obuild for my own libraries. However, that was in the context of obuild using tsdown as a dependency, which would mean obuild inherits all the features tsdown already offers. As things stand now, does obuild actually have all those features? (e.g watch mode)

This "migration from unbuild" issue at least sounds very hostile not not in good faith towards collaboration

The discussion about collaboration between obuild and tsdown took place last week, but you’ll notice that this issue was actually opened last month, and its corresponding PR (#163 (comment)) has intentionally seen no progress so far.

[pi0]

Rolldown’s core functionality is already stable enough at this point.

I truly root for rolldown but frankly, it is not as stable as rollup for bundling dependencies without risk of (production dist) regressions. With my very limited trial, I found rolldown/rolldown#4166 and rolldown/rolldown#4575 both could break our packages if migrated to the new stack. I'm certain all will be fixed, and I truly appreciate all the work on rolldown, but it takes time.

Certain features are still missing in obuild—for example, CJS support

Not supporting CJS in the new major version is by design (and for good!), not a lack of a feature. Nothing really hard to have specially since both rolldown and rolldown-plugin-dts fully support CJS output!

watch mode

One of the unique features of unbuild is stub/watchless mode. With obuild, we will go with the passthrough mode by default, and I know you don't like this approach, and I fully respect that.

---

Honestly, I don't want to pick a fight here and as you know open to work together, but please respect that obuild is the successor of unbuild and do not do a hostile action (against unbuild users to migrate to tsdown) with #163.