Closed snorkpete closed 4 years ago
Your diagnostics report shows that you are manually specifying Wallaby configuration where you should not need to. Could you please try switching to use automatic configuration as we expect that will solve your issue.
Can I just say, you guys f*cking rock!!! ?
Thanks for the speedy reply, and if you can't tell yet, switching to automatic configuration worked!
You guys are a life saver! Since I've started using wallaby.js, i can't work without it - it's become vital to my workflow. Running tests any other way just seems so slow in comparison - almost unusably slow.
Keep up the awesome work!
In my project setup, I have an internal npm module
(roomblock-components)
than contains Vue components as.vue
files. However, I'm intentionally not compiling the Vue components to es5 before publishing the internal npm module - this module is only to be used as a means of sharing code between two specific projects, and not as a general purpose npm module. This is generally not a problem - my build system is configured to compile the Vue files in this shared npm module, and I configured Jest so that it transforms files within theroomblock-components
project as wellHowever, I can't seem to configure Wallaby.js to do the same. I can run Jest on the command line and it will run through all my tests without issue, but when trying to do the same with Wallaby.js, I can't seem to get it to work. When encountering any test that tries to use a Vue component from the npm module
roomblock-components
I get the error:Funnily enough, looking at the stack trace from the error, i'm seeing the error triggered from
jest@0.4.3
, which i don't quite understand, but that might be an unrelated issue.I've since tried adding both
@babel/preset-env
andbabel-preset-env
to my project, and using different combinations of preset (env
,@babel/env
,@babel/preset-env
,babel-preset-env
) in my jest configuration, but none of them seemed to work.At this point, I'm not sure what to try next. I attempted to just bypass the problem altogether and just resort to running the tests using Jest on the command line, but having worked with Wallaby.js, using command line just is just way too slow. (Wallaby.js has spoilt me completely)
Below is the my jest configuration file and the output from the wallaby diagnostic report. Please note that I've edited both to remove some potentially confidential code, but otherwise, this is what i'm using. Unfortunately, the project is internal and is also using a number of internal libraries that I can't share so it's difficult to share a full project that clearly reproduces the error. I can try to provide as much information as you might need to help point me in a direction of a solution, but I do apologize in advance for not having a full project available.
I'm also not very comfortable in the land of Babel and transpilers and build systems in general - i'm just using tools and configuration that were provided to me by other internal teams - so there may be an obvious solution that I'm just clueless about. Unfortunately, no one else uses Wallaby, so it's not easy to get internal support, hence why I'm stuck.
Stacktrace from failed tes
Jest Config
Wallaby diagnostics report