Skip to content

Modernize repository #206

Open
Open

Description

@rubensworks

While the software in this repo still works, we should modernize the code and bring it up to modern standards:

Activity

  1. jitsedesmet commented on Jul 17, 2026

    @jitsedesmet

    It might be worthwhile adding types first such that agentic tools can support you better.

  2. jitsedesmet commented on Jul 30, 2026

    @jitsedesmet

    Renovate seems to already be enabled. (verified in online portal). Only thing different is that we now specify the json-shema as well.

  3. jitsedesmet commented on Jul 31, 2026

    @jitsedesmet

    @rubensworks is dual packaging/ converting to ESM also part of the modernization strategy?

  4. rubensworks commented on Jul 31, 2026

    @rubensworks
    MemberAuthor

    No, doesn't seem high prio to me, since this is not really used as a library.

  5. jitsedesmet commented on Aug 5, 2026

    @jitsedesmet

    Seems like the imports of this repo violate the monorepo package API boundaries. Some lib files import the lib files of another package directly. Since the code is mostly used for it's binaries, it has kept under the radar, but when using the code as a lib, it's quite an anti-pattern. Ofcource, if we start exposing more functionality, the API we need to keep stable grows.

  6. jitsedesmet commented on Aug 7, 2026

    @jitsedesmet

    Another interesting task might be to look whether we still need to depend on lodash. Old codebases can often migrate to modern EcmaScript + little util functions instead of depending on lodash.

  7. added a commit that references this issue on Aug 20, 2026
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