History

Chris Grimmett 1d35f4b33d add packagejson to the build		2024-03-29 21:01:24 -08:00
..
app	add gitea ci	2024-03-28 23:28:02 -08:00
assets	add gitea ci	2024-03-28 23:28:02 -08:00
public	upgrade to bulma 1	2024-03-28 03:48:46 -08:00
.dockerignore	upgrade to bulma 1	2024-03-28 03:48:46 -08:00
.eslintrc.json	init	2024-01-20 08:16:14 -08:00
.gitignore	init	2024-01-20 08:16:14 -08:00
.nvmrc	init	2024-01-20 08:16:14 -08:00
CHECKS	init	2024-01-20 08:16:14 -08:00
LICENSE	init	2024-01-20 08:16:14 -08:00
README.md	init	2024-01-20 08:16:14 -08:00
app.json	init	2024-01-20 08:16:14 -08:00
next.config.js	init	2024-01-20 08:16:14 -08:00
package.json	add packagejson to the build	2024-03-29 21:01:24 -08:00
pnpm-lock.yaml	add gitea ci	2024-03-28 23:28:02 -08:00
tsconfig.json	remove things stoppping a build	2024-02-27 07:52:43 -08:00

README.md

futureporn-next

Dev notes

When adding a new module via pnpm, docker compose needs to be restarted or something. I'm not sure the exact steps just yet, but I think it's something like the following.

pnpm add @uppy/react
docker compose build next

fp-next | Module not found: Can't resolve '@uppy/react'

hmm... It looks like I'm missing something. Is the new package not getting into the container? Maybe it's something to do with the pnpm cache?

Must we build without cache?

docker compose build --no-cache next; docker compose up

YES. that solved the issue.

However, it's really slow to purge cache and download all packages once again. Is there a way we can speed this up?

make it work
make it right
make it fast