Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define path to package.json #85

Closed
daribock opened this issue Sep 16, 2022 · 3 comments
Closed

Define path to package.json #85

daribock opened this issue Sep 16, 2022 · 3 comments
Labels
duplicate This issue or pull request already exists feat: workspace p2-nice-to-have Not breaking anything but nice to have (priority)

Comments

@daribock
Copy link

Is your feature request related to a problem? Please describe.
The project I am working on uses kotlin for the backend and therefore the ui is in a seperate folder and the package.json is therefore not in the root of the project. This is why I am getting errors when running the tests.
image

Describe the solution you'd like
My suggestion for this solution would be either one of these two options:

  1. Auto detect package.json
  2. Option to manually define the path to package.json
@daribock daribock added the p2-nice-to-have Not breaking anything but nice to have (priority) label Sep 16, 2022
@leonie-koch
Copy link

Is there any update on how to run the vitest runner, if the web folder is not in root?

@zxch3n
Copy link
Member

zxch3n commented Feb 9, 2023

You can try using VS Code workspace as a workaround for now

@zxch3n zxch3n added the duplicate This issue or pull request already exists label Feb 9, 2023
@zxch3n
Copy link
Member

zxch3n commented Feb 9, 2023

Close this in favor of #101

@zxch3n zxch3n closed this as completed Feb 9, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Feb 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
duplicate This issue or pull request already exists feat: workspace p2-nice-to-have Not breaking anything but nice to have (priority)
Projects
None yet
Development

No branches or pull requests

3 participants