Hi,

in the past I've done mainly backend-work, but in my new project I also have to do some frontend-stuff for web-apps.

In practice that means that I have to generate Javascript from Perl in the form that I have a here-document containing Javascript-code with a few Perl-variables interpolated.

What drives me nuts is that my workflow is so inefficient, e.g. I make some changes, have a look at the new page in the browser only to find in the JS-console that I have made a trivial syntax-error in my Javascript (my dev-environment is vi and firefox with firebug).

So I wonder is there a better way to do this? Is there any hack that I could somehow syntax-check my JS-snippets that are embedded in a perl-module?

Or does someone have any suggestions on how to do this properly?

Many thanks!

In reply to What is your Javascript-workflow? by morgon

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.