psychollama / freighter Goto Github PK

In my experience, each package typically manages its own compiler tooling. That means using a framework like tsdx, create-react-app, or managing something bespoke (ugh, ponder). Whatever the case, monorepo level tooling barely buys anything and it certainly doesn't have to be part of the freighter framework. I'd like to rip it out.

It was worth a shot at least.

The offending template:

{
  "husky": {
    "hooks": {
      "pre-commit": "lint-staged"
    }
  },
  "lint-staged": {
    "*.js": ["freighter-scripts lint --fix", "git add"]
  }
}

And this should be another issue entirely, but make *.js inclusive of TypeScript files and remove the git add step (lint-staged does it automatically these days).

In practice I'm using Freighter with smaller generators (tsdx, create-react-app) that each have their own test scripts, and they run in radically different ways. CRA is especially grumpy when you have more than one Jest in the workspace.

Jest Projects have proven the most unreliable and annoying part of Freighter. I'd rather rip it out and replace it with a bulk npm run test that runs across the monorepo. Bonus points if it runs in parallel.