Feedback

Whether you’ve found a bug, have a performance issue, or just want to suggest an improvement, here’s how you can open a helpful issue

Reporting Issues

Upgrade viabl

Try upgrading viabl to the latest version with viabl update to update the render and server, or npm i @viablkit/cli to update your cli. This might fix your problem without having to open an issue.

terminal

viabl update

If the issue still persists after upgrading, continue to the next step.

Review Existing Issues

First take a minute to check if the issue has already been reported. Don’t open a new issue if it has already been reported, it saves time and helps us focus on fixing things faster.

If you find a related issue, add a 👍 reaction or comment with extra details instead of opening a new one.

Report the Issue

If no one has reported the issue, please open a new issue or suggest an improvement.

Please provide as much detail as possible, including:

A clear and concise title
A code example or steps to reproduce the issue
The version of viabl you are using (run viabl --version)
The version of render and viable server you are running (run viabl version-info)
A detailed description of the issue (what happened, what you expected to happen, and what actually happened)
The operating system and version you are using

For MacOS and Linux: copy the output of uname -mprs
For Windows: copy the output of this command in the powershell console: "$([Environment]::OSVersion | ForEach-Object VersionString) $(if ([Environment]::Is64BitOperatingSystem) else )"

The viabl team will review your issue and get back to you as soon as possible!