![]() Incremental rebuild (described soon) of a single file in a project is around 70ms too.Ĭleaning the artifacts should be instantaneous. ![]() No-op build (when no file's changed) should be around 15ms. inserting rescript into your existing JS build pipeline). This doubles when you use the JS rescript wrapper which comes with a watcher, which is practically faster since you don't manually run the build at every change (though you should opt for the raw rescript.exe for programmatic usage, e.g. Raw rescript.exe build on a small project should be around 70ms. Our editor plugin finds and uses this native rescript.exe for better performance. ![]() This side-steps Node.js' long startup time, which can be in the order of 100ms. If you don't need the watcher, you can run said rescript.exe. It's located at node_modules/rescript//rescript.exe. The lower-level, watcher-less, fast native rescript is called rescript.exe. #Node js compile to exe plusRescript itself is a Node.js wrapper which takes care of some miscellaneous tasks, plus the watcher. The file contains the low-level compiler commands, namespacing rules, intermediate artifacts generation & others. ReScript reads into bsconfig.json and generates the Ninja build file in lib/bs. In this regard, Ninja's a great implementation detail for rescript. ![]() Ninja is like Make, but cross-platform, minimal, focuses in perf and destined to be more of a low-level building block than a full-blown build system. ReScript itself uses a build system under the hood, called Ninja. Screenshot of bstracing result Under the Hood ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |