parse.nodeToString incorrectly calculates range

[jrburke]

In particular, if there is no comment or content above the requirejs.config call, it calculates the start value off by one as the preamble incorrectly includes as \n for zero line requirejs.config calls.

Found by @robdodson, in yeoman/grunt-bower-requirejs#36

[jrburke]

Fixed in master, can be tested via the master link: https://raw.github.com/jrburke/r.js/master/dist/r.js

[also]

This still doesn't work well.

Given

requirejs({});

parse.nodeToString returns

{});

requirejs({}

Given

requirejs(
{});

parse.nodeToString returns

{});

{}

and finally, given

requirejs(
{}
);

parse.nodeToString returns

{}

{}

which is the only variation that works.

I was trying to use mainConfigFile with a file generated from JSON, so it had no line breaks.

[jrburke]

Putting it 2.1.9 bucket for evaluation.