Skip to content

more ideas for cleaning up the project ahead of v3 #1869

Closed

Description

@beeequeue

related to #665

the ideas ive looked at or started working on are

  • migrate from yarn v1 to pnpm
    • the main part i would need help with for this is the publishing flow for the repository, since its very easy to miss some part of it
  • build with tsdown instead of preconstruct
  • replace enquirer with @clack/prompts (Migrate away from enquirer #1861)
  • replace @inquirer/external-editor with launch-editor
  • update eslint config
    • would either remove standard config and just use the recommended rules in each plugin, or move to neostandard
    • or i could move it to use oxlint if that sounds interesting
  • run knip on the project
  • replace micromatch with picomatch or zeptomatch
  • replace spawndamnit with tinyexec

let me know which ones sound good and ill revive or start working on them :)

Activity

  1. Andarist commented on Mar 4, 2026

    @Andarist
    Member

    build with tsdown instead of preconstruct

    It becomes less and less important nowadays but Preconstruct has some unique features I really like so this one might be a hard sell. That said, Preconstruct does need some love and modernization. There is room for improvement there too

    migrate from yarn v1 to pnpm

    This can be done at any time, I'd focus now on revamps that affect published sources.


    I think the other things on your list are pretty OK so I'd probably quickly land PRs addressing those.

  2. beeequeue commented on Mar 4, 2026

    @beeequeue
    MemberAuthor

    just so i can learn, what does preconstruct do that tsdown/other bundlers don't?
    i saw preconstruct dev being used in places but couldn't tell what the difference would be to just running a build command :^)


    i'd prioritize pnpm since i don't like using package managers that don't disable postinstall scripts by default and yarn v1 is frozen since 2021.
    i do have a branch locally with it done already with the one question being the publishing since i know little about this project's worklows


    but if you don't want to look at package management yet i will start on some of the other points

  3. beeequeue commented on Mar 11, 2026

    @beeequeue
    MemberAuthor

    i pushed my tsdown migration branch here so you can look at it

  4. bluwy commented on May 4, 2026

    @bluwy
    Member

    @beeequeue can you merge this into #1945? We can discuss some points in discord if there's some you didn't get consensus on yet.

  5. beeequeue commented on May 4, 2026

    @beeequeue
    MemberAuthor

    i added the pnpm migration to v3 as the final topic from here, tsdown will wait for v4 unless plans change

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions