You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is the error I got when I originally tried to npm install vitest, then run docker:
Error: Cannot find module @rollup/rollup-linux-x64-musl. npm has a bug related to optional dependencies (https://github.com/npm/cli/issues/4828). Please try `npm i` again after removing both package-lock.json and node_modules directory.
I only got this when I tried to run docker compose up. Not when I was running the vite server on my local machine.
During dev meeting on 04/28, Benny said he tried testing this PR's docker compose up and it didnt work on his machine. He mentioned docker on windows and mac uses different linux binaries under the hood.
I made a new commit. This time instead of removing node_modules and package-lock.json and reinstalling, I took the package.json and package-lock.json from the develop branch, and used the npm cli to install packages one at a time, testing docker with each new install to make sure the @rollup/rollup-linux-x64-musl missing module error didn't occur again.
For some reason no issues came up this time 🤔
@bennyv8 Could you try testing and reviewing again?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #670
Changes
reinstalledpackage-lock.jsonandnode_modulesMinor changes:
node_modulesto docker compose. The vite container wasn't working on windows before, and naming the volume helped to debug it.installed packageeslint-config-prettierto fix a linter issue, since eslint got updated to version 9.25.1 in the new package-lock.jsonlinted frontend files - mostly effected changes to tailwind classnames order in some componentsHow it works
First, make sure you have node.js installed on your machine, then run
npm installin the/frontendfolder. This should install the new dependencies.In the
/frontendfolder, run the command:It should say all tests pass, although there are some warnings:

How to test this PR
/frontendfolder and runnpm installnpm run testworks.node_modulesto get it to work:rm -rf node_modules && npm i