Skip to content

feat: tidy repo and synchronize deps#6

Merged
ryanwolhuter merged 22 commits intomainfrom
tidy-repo
Feb 18, 2026
Merged

feat: tidy repo and synchronize deps#6
ryanwolhuter merged 22 commits intomainfrom
tidy-repo

Conversation

@ryanwolhuter
Copy link
Contributor

@ryanwolhuter ryanwolhuter commented Feb 18, 2026

There were some dependency related issues happening in places where we import code from this repository in the main powerhouse monorepo.

  • dependencies were specified as peers instead of workspace
  • packages were published at different versions
  • packages had old versions of dependencies that also exist in the monorepo, leading to conflicts
  • "bundler" module resolution in the tsconfig.json without a bundling step meant that some of the exported code is not compatible with the code in the monorepo.

There was also no linting/formatting set up in the repo, and no test step in the ci.

I have added a new release workflow which will publish the dependencies in lockstep with each other, so there will no longer be issues with peer dependencies / mismatched versions.

I have fixed the above and added the other pieces. Everything builds and compiles, all tests pass.

Signed-off-by: ryanwolhuter <dev@ryanwolhuter.com>
Signed-off-by: ryanwolhuter <dev@ryanwolhuter.com>
Signed-off-by: ryanwolhuter <dev@ryanwolhuter.com>
Signed-off-by: ryanwolhuter <dev@ryanwolhuter.com>
Signed-off-by: ryanwolhuter <dev@ryanwolhuter.com>
Signed-off-by: ryanwolhuter <dev@ryanwolhuter.com>
Signed-off-by: ryanwolhuter <dev@ryanwolhuter.com>
Signed-off-by: ryanwolhuter <dev@ryanwolhuter.com>
Signed-off-by: ryanwolhuter <dev@ryanwolhuter.com>
Signed-off-by: ryanwolhuter <dev@ryanwolhuter.com>
Signed-off-by: ryanwolhuter <dev@ryanwolhuter.com>
Signed-off-by: ryanwolhuter <dev@ryanwolhuter.com>
Signed-off-by: ryanwolhuter <dev@ryanwolhuter.com>
Signed-off-by: ryanwolhuter <dev@ryanwolhuter.com>
Signed-off-by: ryanwolhuter <dev@ryanwolhuter.com>
Signed-off-by: ryanwolhuter <dev@ryanwolhuter.com>
Signed-off-by: ryanwolhuter <dev@ryanwolhuter.com>
Signed-off-by: ryanwolhuter <dev@ryanwolhuter.com>
Signed-off-by: ryanwolhuter <dev@ryanwolhuter.com>
Signed-off-by: ryanwolhuter <dev@ryanwolhuter.com>
Signed-off-by: ryanwolhuter <dev@ryanwolhuter.com>
}),
);

await bench.warmup();
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

warmup has been moved to an optional argument, see instantiation of bench above

{
"name": "benchmarks",
"version": "0.1.0",
"private": true,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

made this private so that it does not get published. gave it the same version as the rest of the monorepo for consistency

test: {
browser: {
provider: "playwright",
provider: playwright(),
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the api for setting up this type of test has changed since the old version of vite that was used previously. this config produces the same result.

"scripts": {
"build": "tsc",
"test": "PG_CONNECTION_STRING=postgresql://postgres:password@localhost:5555/analytics vitest run"
"test:pg": "PG_CONNECTION_STRING=postgresql://postgres:password@localhost:5555/analytics vitest --run ./**/*.test.ts"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

renamed to test:pg so that this test is not run by the normal test-ci command in the check commit workflow

environment: "node",
testTimeout: 5000,
setupFiles: "./test/vitest.setup.ts",
poolOptions: {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not so sure what this was doing before, but this option has been removed from the vitest config in the current version. it looks to me like the tests all pass in a reasonable amount of time as expected.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was here in the case that we used a single PG db backend in test (like test:pg).

Signed-off-by: ryanwolhuter <dev@ryanwolhuter.com>
@ryanwolhuter ryanwolhuter merged commit 433814c into main Feb 18, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants