fp/packages
CJ_Clippy 7793e38878
ci / build (push) Failing after 1s Details
progress
2024-08-13 13:18:01 -08:00
..
image progress 2024-08-13 13:18:01 -08:00
infra capture progress 2024-07-22 18:59:41 -08:00
meal progress 2024-07-30 12:34:25 -08:00
old progress 2024-07-30 12:34:25 -08:00
scout bot progress 2024-08-06 17:13:58 -08:00
storage progress 2024-07-30 12:34:25 -08:00
taco use internal ts package 2024-07-19 00:01:06 -08:00
types fp/factory can now concatenate 2024-08-09 16:28:37 -08:00
utils progress 2024-07-30 12:34:25 -08:00
video fix scout dockerfile 2024-07-16 02:46:44 -08:00
worker bot progress 2024-08-06 17:13:58 -08:00
README.md differentiate services vs packages 2024-07-27 16:42:09 -08:00

README.md

Futureporn node packages

Each folder here is an individual node package, each of which can reference each other. One reason we do this is to share utility functions between packages.

See https://pnpm.io/workspaces

These are Typescript internal packages, which means they export typescript, not javascript. The TS-to-JS build step occurs in the package which is doing the import.

Also see ../services/* which are also pnpm packages, with the diffentiation that those are full-fledged programs meant for running

Also see ../pnpm-workspace.yaml for more notes