LiquidDebug provides a stack trace of executed Liquid code when an error occurs, supplementing the [typically vague] default error format provided by Liquid.
It is not suitable for a production environment as it makes no effort to account for performance or memory leak issues and so should only be used in a development environment when debugging specific issues.
Add the following to your Gemfile:
gem 'liquid_debug', '~> 0.1.1'
Include the LiquidDebug extension (e.g. in an initializer or in config/application.rb):
# config/initializers/liquid_debug.rb
require 'liquid/debug' if Rails.env.development?
You should now see something like this in your server output when a Liquid error occurs:
FAQs
Unknown package
We found that liquid_debug demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Ransomware payment rates hit an all-time low in 2024 as law enforcement crackdowns, stronger defenses, and shifting policies make attacks riskier and less profitable.
Security News
require(esm) backported to Node.js 20, easing the transition to ESM-only packages and reducing complexity for developers as Node 18 nears end-of-life.
Security News
PyPI now supports iOS and Android wheels, making it easier for Python developers to distribute mobile packages.