[Question] Making JS Files a Built-in module about txiki.js HOT 6 CLOSED

Alas that's unavoidable in this case. You can use globals, or bundle all your libs in a single bundle for example.

In here the polyfill, core and run-main are 3 separate bundles each containing a bunch of stuff.

from txiki.js.

Understood thanks, you've been very helpful.

from txiki.js.

Then you convert the resulting polyfills.js file into polyfills.o code using qjsc.

Not quite, this generates a polyfills.c file, it's C source code, basically an array with the JS bytecode.

It's included in the build here:

So it gets compiled with the rest of the binary.

from txiki.js.

I was thinking that the -c flag is needed to convert to C code.

-c
Only output bytecode in a C file. The default is to output an executable file.

https://bellard.org/quickjs/quickjs.html#qjsc-compiler

from txiki.js.

I was thinking that the -c flag is needed to convert to C code.

Correct, it outputs a C file. You can see it here: https://github.com/saghul/txiki.js/blob/master/src/bundles/c/core/run-main.c

from txiki.js.

When I convert a JS file to C, all its dependencies are also included in C. How did you avoid this?

I have two libraries:

• lib-A.js
• lib-B.js

lib-A.js needs lib-B.js.

When I compile, the lib-A.c file contains both its own code and lib-B.js, while lib-B.c contains only its own code.

It's actually normal, but it's causing problems with it.

I can avoid this like this: I create index.js file and import it into two files so I have a single module.c file that contains both lib-A.js codes and lib-B.js codes.

The minus side of this is that index.js codes that will not be used will be added and the resulting C file will be large.

from txiki.js.