Preprocess Javascript on-the-fly

[Kevin Ingwersen (Ingwie Phoenix)]

I am currently looking into using oj, a Objective-C like syntax for JS. Why I didn’t use Objective-J? Its not nodejs-friendly.

But oj lacks a preprocessor…but I need one. Actually, I only need one thing: #include.

I went and browsed npm, but I only found one preprocessor, but it required slashes - which does not look very clean to me. The one I found wanted me to do:

// #ifdef A
…
// #endif

I just want do something like

#include <file>

or

#ifdef A
…
#endif

If I can’t find one, I’ll just write my own…but it’s a bit sad.

Does anyone know a proper, javascript-based preprocessor? I want to use it in a middleware and preprocess the file, before giving it to oj.

Kind regards, Ingwie

[Aria Stewart]

> On Oct 28, 2014, at 6:19 AM, Kevin Ingwersen (Ingwie Phoenix) <ingwi...@googlemail.com> wrote:
>
> I am currently looking into using oj, a Objective-C like syntax for JS. Why I didn’t use Objective-J? Its not nodejs-friendly.
>
> But oj lacks a preprocessor…but I need one. Actually, I only need one thing: #include.
>
> I went and browsed npm, but I only found one preprocessor, but it required slashes - which does not look very clean to me. The one I found wanted me to do:

Have you considered just using CPP?

https://gist.github.com/aredridel/e288f76b8f80ed8dc36a

[Ryan Schmidt]

On Oct 28, 2014, at 9:32 AM, Aria Stewart wrote:

> On Oct 28, 2014, at 6:19 AM, Kevin Ingwersen wrote:
>
>> I am currently looking into using oj, a Objective-C like syntax for JS. Why I didn’t use Objective-J? Its not nodejs-friendly.
>>
>> But oj lacks a preprocessor…but I need one. Actually, I only need one thing: #include.
>>
>> I went and browsed npm, but I only found one preprocessor, but it required slashes - which does not look very clean to me. The one I found wanted me to do:
>
> Have you considered just using CPP?
>
> https://gist.github.com/aredridel/e288f76b8f80ed8dc36a

cpp should not be used for non-C code.

http://web.mit.edu/ghudson/info/cpp.whynot

[Alex Kocharin]

When I did that, I used GNU m4 for this. Maybe it'll help in your case as well.

Using GCC preprocessor isn't a bad thing either, but it'll have to be fine-tuned to do that.


28.10.2014, 17:26, "Kevin Ingwersen (Ingwie Phoenix)" <ingwi...@googlemail.com>:

> --
> Job board: http://jobs.nodejs.org/
> New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md
> Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> ---
> You received this message because you are subscribed to the Google Groups "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+un...@googlegroups.com.
> To post to this group, send email to nod...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/A3D61862-4B72-4487-9C99-D7DED8ED923E%40googlemail.com.
> For more options, visit https://groups.google.com/d/optout.

[Axel Kittenberger]

Why not use the javascript VM as preprocessor? Node is about putting more javascript into javascript anyway.

Every line starting with '#' is coded in the preprocessor context, every line that isn't, is for the result.

I wrote it in a way, so line numbers are ought to be preserved unless an include( ) happens, in that case line numbers go a little amiss.

example input.js:

For example:

preprocessor.js:

-----------------------------

var fs = require( 'fs' );

var vm = require( 'vm' );

var file = fs.readFileSync( 'input.js' ).toString( );

var lines = file.split('\n');

var skipped = '';

var code = [ ];

var result;

for( var ln in lines )

{

var line = lines[ ln ];

if( line[ 0 ] === '#' )

{

lines[ ln ] = line.substr( 1 );

skipped += '\\n';

}

else

{

lines[ ln ] =

'code.push("'

+ skipped

+ line.replace( /\"/g, '\\"' ).replace( /"/g, '\\"' )

+ '");';

skipped = '';

}

}

lines.push( 'code; ');

result =

vm.runInNewContext(

lines.join( '\n' ),

{

code : code,

require : require,

include :

function( filename )

{

code.push( fs.readFileSync( filename ) );

}

}

)

.join( '\n' );

console.log( result );

-------------------

Do with result what you want, like using it in the http server module, cache it, etc. you might wrap some async code to replace readFileSync() with async alternatives in the flow control of your choice. 

------------------------

#var test = require( './test' );

#if( test ) {

console.log( '"hello"' );

#}

console.log( 'world' );

#include( 'include-me.js' );

-----------------------

example test.js :

------------------------

// just contains a yes/no switch

module.exports = true || false;

----------------------------

Handing the preprocessors own require function to the to be preprocessed file might be a little naive and have quirky effects if they use the same files, I just suppose its trusted code anyway, but for a starter it works. Might be replaced with a custom require if so desired.

One can also directly alter the 'code' array in preprocessor context to add custom stuff.

[Jarrod Overson]

I assume you are talking about this module : https://www.npmjs.org/package/preprocess

I've updated and published 2.1.0 to accommodate unwrapped directives (when used as a library). The slashes (and other formats) are there to keep the files parsable by their destination environments regardless of whether or not they have been preprocessed.

--

Jarrod Overson 

tw | gh | g+ | li

[Kevin Ingwersen (Ingwie Phoenix)]

That is a very impressive example - i wonder why thsi method is not its own module anyway =p I will try and test this! Thank you a lot for this solution. I never saw any ude for the vm module…well, now I do.

--
Job board: http://jobs.nodejs.org/
New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
---
You received this message because you are subscribed to the Google Groups "nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+un...@googlegroups.com.
To post to this group, send email to nod...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/CABg07fthq%2BerYUggubCSBJoKE%2BiK9eBc67A690on3R85cNmQwQ%40mail.gmail.com.

[Kevin Ingwersen (Ingwie Phoenix)]

Yes, that’s the one that I found originally. So are you saying that I could use the directives without using comments at all? Because, to me, it doesn’t look like a real preprocessor if there are comment dashes infront of it - that might only be a personal taste, and due to my long work in C++ over all the last months...

To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/CAJoBgEg4D7nyvRLos-xK%3DMww3c3Rew9fWsM%3DfST1%2B5ORQr__tw%40mail.gmail.com.

[Louis Santillan]

Crockford offered up JSDev [0].  And as mentioned, using GNU cpp "can" have drawbacks.  Alternatively, you may want to investigate using ucpp [1] which will do C99 style preprocessing without doing parsing or compilation.

[0] https://github.com/douglascrockford/JSDev

[1] https://code.google.com/p/ucpp/

To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/1A2FDCDF-C36E-40BD-8205-875D5FD6DA43%40googlemail.com.

[Kevin Ingwersen (Ingwie Phoenix)]

Here you have it: https://github.com/IngwiePhoenix/connect-oj/blob/master/pp.js

You can copy it, put it in your project and use it. Its simple and pretty cool. :) It does not just work with JS, but really everything. I am using it to preprocess .oj files, mainly to use #include() to import base classes.

Am 28.10.2014 um 20:13 schrieb Axel Kittenberger <axk...@gmail.com>:

--
Job board: http://jobs.nodejs.org/
New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
---
You received this message because you are subscribed to the Google Groups "nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+un...@googlegroups.com.
To post to this group, send email to nod...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/CABg07fthq%2BerYUggubCSBJoKE%2BiK9eBc67A690on3R85cNmQwQ%40mail.gmail.com.