-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
"MODULE NOT FOUND" error for test-dependencies #105
Comments
Can you manage to get the same error with https://github.com/rtfeldman/elm-spa-example ? Do you need to make changes for it to error for you, or does it error out of the box? |
Closing due to no reply. |
I am having similar problems: the project compiles and tests just fine, but the plugin complains:
The "blue bulb" asks me if I want to install
The directory contains both TypeScript files (in I have tried the |
OK, now I can see the problem. This plugin expects the tests to be in It looks my colleague who was coding the code I am working with right now, he was using Intellij Idea plugin, because I can see the {
"test-directory": "test/elm"
} |
I'm having the same issue, would love to know if there is a work around. The project I'm working on has the test file alongside the regular file with the |
No, there is no work around, test detection needs to be implemented, which should be a bit more straight forward since the latest version. |
Expected Behavior
I have
elm-explorations/test
in mytest-dependencies
in elm.json. That should be sufficient for my test files to be able to import modules from that package without errors.Current Behavior
The following errors show up in the Problems pane in VS Code (although compiling and running elm-test work just fine):
Steps to Reproduce
I have the following elm.json:
As you can see from
source-directories
, the file structure isIt's inside
SortTests.elm
that this error appears (and other files in that directory). I can get rid of the error by movingelm-explorations/test
andelm/random
into the corresponding fields underdependencies
instead of undertest-dependencies
.Your Environment
The text was updated successfully, but these errors were encountered: