DTC 08-20-2024

[belsrc]

Discuss Folder Structure PRs

Note

Things like geo are a very specialized type of work. For things like coordinates since they are so specialized.

User peer-deps for things like turf. * re-exports are dirty.

If there is a coord validator, how would I know if I go to geo or validators?
Not a hard line rule currently. Maybe validator is just for primitives and things like that.

We could have TS narrowing functions in the validators.

We could publish the tooling configs. The expectation is that the public isn't going to care about or use it. But they can be used internally to the company for all projects. Could be a challenge with the resolution of the paths in the config.

Discuss Doc Frameworks

Note

More pipelines for the deploying the docs and ladle stuff. No hard feelings at this time.

Determine Tooling Needs/Wants

Do we want current parity? Do we want to swap out to different/newer tools? etc

Note

Modern and/or specialized tooling. Biome, left-hook, ls-lint, markdown-lint, turbopack, et. al.

Need to go back through the Biome comparison doc and make sure that it is updated to current Biome release. Will need to walk through it and determine yay/nay on if its a "live without" to make final determination on a split job or solely Biome.

Determine pipeline tasks

Note

In prepush still use things like lint check, formatting and types(?)

Testing, linting, security checks (snyk), dependency checks, code quality (non-blocking)

Something that can regression test the size of the bundle. React does bundle size regression.
Maybe there is something that can check the size of the dependency libs?

Need to make sure that we have remote caching is setup.

https://biomejs.dev/recipes/continuous-integration/
(https://github.com/marketplace/actions/run-biome-with-reviewdog ??)
https://github.com/marketplace/actions/run-eslint (see note for native)
(https://github.com/marketplace/actions/run-eslint-with-reviewdog ??)
https://github.com/marketplace/actions/run-tsc-from-node_modules-with-reviewdog
https://github.com/marketplace/actions/code-coverage-with-reviewdog
https://github.com/marketplace/actions/run-markdownlint-with-reviewdog

Anything else??

How are we building? Are we bundling things correctly? This would basically just for TS > JS. We don't really need to bundle per say. We plan to just support ESM. Will need to make sure that vanilla extract will work if you "compile" from TS to JS