You should be able to pop the offending code into a BEGIN block, replacing use with require and wrap with eval to catch any failures:

BEGIN {
  eval {
    require Stash;
    require Dumper;
    $Dumper::Indent = 1;
    Dumper.dump( Stash.stash() ) };
}

[download]

Another thing I tend to do with debug code is set a constant (such as DEBUG) and make sure all of my debug code is wrapped up with if DEBUG statements, which completely strips the code out when not running in debug mode

In reply to Re: Template::Toolkit - catching errors when plugin is missing? by SimonPratt
in thread Template::Toolkit - catching errors when plugin is missing? by Skeeve

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.