![]() ![]() Nothing works or too many different errorsĬonfiguring a new tool for a project may be challenging. Once downloaded, the plugin version may be installed as described in the corresponding document section.Īfter you have installed the previous version and restarted your IDE, uncheck the Automatically update this extension checkbox. If you are downgrading to version 1.0.17 in Visual Studio 2019, the URL will be. For example, if you are downgrading to version 1.0.17 in Visual Studio 2017, the URL will be. To download the previous version for Visual Studio, use the following link:, where aaaa is your Visual Studio version. For example, if you are downgrading to version 1.0.34, the URL will be. To download the previous version for IntelliJ platform IDE, use the following link. You may find it by opening Settings - Plugins for IntelliJ platform IDEs or Tools - Extensions and Updates in Visual Studio and locating wallaby.js there. If you are using IntelliJ platform based IDE or Visual Studio, try downgrading your plugin version.įirst, check what’s your current plugin version. Clearing the Wallaby cache should never be required if this solves your problem, please report an issue. If you use another editor, you may clear the Wallaby cache by changing the timestamp on your project’s package.json. If you use a JetBrains editor, you may clear the cache with the Help | Wallaby.js | Reset Wallaby Cache menu item. If you are a VS Code user, you can clear the cache with the Wallaby.js: Reset Wallaby Cache command. The Wallaby cache is automatically monitored for issues and repaired seamlessly in the background. Wallaby has its own cache for transformed and changed files. Please refer to your testing framework documentation for further information on whether it uses a cache and if so, how to reset it. For example, if you use jest, you may clear jest cache from the command-line with npx jest -clearCache. Often, you may experience issues because your testing framework has cached a previous result or is serving the wrong file when running your tests. Try resetting your testing framework cache In our experience, questions and issues with attached wallaby config and sample repository are resolved faster. We will have a look, fix the wallaby.js issue or the setup issue, and send you a pull request. Best if you create a repository on GitHub and give us the link to your repo. If you can, please provide us with a small sample project where the error can be reproduced. exports = function ( wallaby ) Configuration issue You may view more debugging information from wallaby.js by setting the trace property to true in your wallaby configuration file and opening the “Wallaby Console” (in VS Code, JetBrains IDEs, Visual Studio, Sublime Text). paste generated report from your clipboard to a newly created issue (feel free to review and edit the report if required).in JetBrains IDEs or VS use Wallaby Help | Wallaby.js | Copy Diagnostics Report menu item.in VS Code, or Sublime editor execute Wallaby Copy Diagnostics Report command.wait until it reports some results (finishes running tests).Wallaby Diagnostics Report is a simple JSON text report that contains some basic information about your Wallaby config and project that is required to start troubleshooting most of Wallaby issues. Problem is an error in your tests/application code, or else a problem with ![]() Ensure tests are passing outside of Wallabyīefore you start troubleshooting, please make sure that your tests are runningĬorrectly (and passing) outside of Wallaby. Unless it’s not something obvious and easily reproducible, please make sure to do as much as you can from the checklist below. Whenever something goes wrong, please report an issue and we will address it as soon as we can. ![]() Wallaby.js issues are registered by using this repository. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |