dcodeIO

Doesn't that just move the issue from encoding to evaluation of the value? `val | 0` yields a 32-bit signed integer value (have you considered using longs?).

I agree that sourcemaps would make this package a lot more usable, but I am currently not planning to invest in this.

**Deprecation notice:** Preprocessor.js has been deprecated in favor of [MetaScript](https://github.com/dcodeIO/MetaScript), a much more JavaScripty way for build time meta programming using JavaScript itself as the meta language. Check out the...

This only matters when compiling with advanced optimizations, isn't an issue otherwise.

Ah, ok. Iirc the Closure Compiler team has also added node externs to the compiler, partly based on this package here, so it might be that.

**Note** that since [node 4.0.0](https://nodejs.org/en/blog/release/v4.0.0/), Buffers are Uint8Arrays backed by an ArrayBuffer anyway. This change effectively renders this module useless (at least for my initial use case), hence it hasn't...

Maybe I miss something, but for a **main.js** with contents ``` js // #include "test.js" console.log('testing include'); // #include "test.js" ``` the file **test.js** is of course included twice, while...

I see. Well, the issue here is that #define is quite a hack currently and does not play well with #ifdef, which is of course bad and I'd need to...

Sorry, this project is not maintained anymore. Give https://github.com/dcodeIO/MetaScript a try!

There is [`heap.reset()`](https://www.assemblyscript.org/stdlib/heap.html#static-members) when using the stub runtime. Must make sure that there aren't any pointers into then-zeroed memory, of course, say in globals, perhaps initialized during `start`.