Colin Quinn
Colin Quinn
I am working on adding component/integration testing to a project that heavily uses pinia and this would be useful for that as well as opposed to manually stubbing it out...
@mattburnett-repo to continue the conversation from the e2e PR where you said the troubleshooting steps didn't work. The root cause of all of this is shared dependencies between the container...
Also you may have to restart vscode after the troubleshooting steps for vscode to pick of the fixed typescript imports from nuxt
I also suspect this bug can be caused if you ever accidentally run `yarn install` in the activist directory. I've done that to myself a couple times.
Yeah, adding that to the docs is a good idea
Found what I think is the root cause: https://github.com/nuxt/nuxt/issues/29744 I tried changing `package.json` to include: ```json "resolutions": { "chokidar": "3.6.0", "playwright-core": "1.45.1" } ``` Reran `yarn install` I can start...
destroying and recreating my environment with `docker-compose rm -f -v --env-file .env.dev` fixed the database issue I ran into
There is still the trouble caused by the local env and container env sharing the same `node_modules`. The right way to fix it IMO is that big directory structure change...
In fact ideally this e2e environment should mirror the prod environment as much as we are able, though obviously it will not be at the same scale as prod.