Top 23 JavaScript Compiler Projects
-
-
webpack
A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
I have written a post about setting up a React project using Parcel as a bundler which can give a more detailed walkthrough about getting a React application up and running from scratch. There are multiple ways to do this but some of the more common build tools include Webpack, Parcel, and Snowpack.
-
-
Static site generator All websites, doesn't matter what they are, fundamentally consists of HTML, CSS, and JavaScript. It doesn't matter what tools or frameworks you use to create your website, the final result needs to be compiled into these file formats in order for the browser to understand and display on the screen. Our blog is no exception. There are two sources of HTML for our blog: _the static _ HTML contents (site header, logo, layout, footer, etc.) and the dynamic HTML contents from the actual blog posts. We need to somehow combine both of these _ static _ and _ dynamic _ HTML sources into a single HTML file at every single build of our app. Static site generator to the rescue!🦸♂️ A _ static site generator _ is a software application that creates HTML pages from templates or components and a given content source during a _ build _ process. There are many static site generators available out there. We will be using Gatsby for our blog. During a build, Gatsby loads JSON data from GraphQL and merges it with components to create HTML pages. These generated pages are then deployed to a web server. When the server receives a request from a browser, it responds with rendered HTML. So the question that needs to be answered now is _ where does the GraphQL data come from? _ 🤔. I'm glad you asked because that's exactly what we're going to explore in the next section.😉
-
Our Clubhouse clone will be built with Parcel, 100ms JavaScript SDK, Tailwind CSS.
-
First we need a way to pull the information for a single post from our MongoDB database. Lets go to the root post.js folder and create a function to do that. We will also be using a library called Marked to convert our current markdown content into HTML to render the blog article directly as HTML on our component.
-
For node you can use pkg to build a binary version of your app that includes nodejs + all depencies, and maybe for db you can replace MySQL with SQLite
-
Apparently Firejail is part of it.
-
Scout APM
Scout APM: A developer's best friend. Try free for 14-days. Scout APM uses tracing logic that ties bottlenecks to source code so you know the exact line of code causing performance issues and can get back to building a great product faster.
-
Project mention: Reverse Babel? Turning Old Javascript to new? | reddit.com/r/learnjavascript | 2021-06-17
-
The title is a bit misleading; the post is about jsc files containing nodejs "bytecode" produced by bytenode.
-
-
Project mention: Clio: a functional, multi-threaded programming language that compiles to JavaScript | reddit.com/r/functionalprogramming | 2021-10-11
I've been working on a functional programming language in the past few years and I'd like to share it with you, would be nice to have some feedback on it! The language is called "Clio" and you can find it here: https://github.com/clio-lang/clio or here: https://clio-lang.org
-
-
-
-
Here is link number 1 - Previous text "BQN"
-
It also have the support for the the Duckuino converter of the RubberDuky scripts https://github.com/Dukweeno/Duckuino
-
Thank you!! If you don’t mind me asking what did you use to compile? I’m using https://github.com/benzino77/tasmocompiler
-
The idea of writing such article popped into my mind while working on my Webflow/React transpiler. All I wanted to do was to take a JS code string and transform it in such way that globals won’t be redefined if already so:
-
serverless-layers
Serverless.js plugin that implements AWS Lambda Layers which reduces drastically lambda size, warm-up and deployment time.
Project mention: Manage Python dependencies in Serverless projects with serverless-layers plugin | dev.to | 2020-12-29One of the first hits when searching for solutions to manage Python dependencies in Serverless projects is the popular serverless-python-requirements plugin. However serverless-layers is a plugin that can work just as well.
-
Project mention: What's something you do a lot in datapacks that you wish was easier? | reddit.com/r/MinecraftCommands | 2021-11-23
There's already things like MCScript and ObjD (both made by the same person), but I'm not really a big fan of their syntax, especially not ObjD. I want to go for something more C-like.
-
DataFormsJS
🌟 DataFormsJS 🌟 A minimal JavaScript Framework, standalone React and Web Components, and JSX Compiler for rapid development of high quality websites and single page applications.
Project mention: Using lit.dev how do I create multiple pages? | reddit.com/r/WebComponents | 2021-11-18 -
Project mention: I want to learn D3. I don’t want to learn Observable. Is that ok? (2019-2021) | news.ycombinator.com | 2021-06-13
As someone building an in-browser notebook I have a lot of opinions on notebook environments. Notebooks serve different purposes, sometimes the notebook itself is the end-goal because the author is creating an interactive tutorial or explaining a complex concept with a bunch of visualizations. Observable is a fantastic tool for that, and the kind-of-Javascript reactive programming system it is built on is a great fit for that.
Outside of that use-case, I think notebooks are great for the first 20% of the effort that gets 80% of the work done. If it turns out one also needs to do the other 80% of the effort to get the last 20%, it is time to "graduate" away from a notebook. For instance if I am participating in a Kaggle machine learning competition I may train my first models in a Jupyter notebook for quick iteration on ideas, but when I settle onto a more rigid pipeline and infra, I will move to plain Python files that I can test and collaborate on.
This "graduation" from notebook to the "production/serious" environment should be straightforward, which means there shouldn't be too much magic in the notebook without me opting into it. Documentation in my eyes is not so different, I should be able to copy the examples easily into my JS project without knowing specifics of Observable and adapt it to my problem. Saying "don't be lazy and just learn Observable", or "you must learn D3 itself properly to be able to use it anyway" is not helpful. Observable being a closed, walled garden doesn't help: not being able to author notebooks without using their closed source editor is a liability that I can totally understand makes it a non-starter for some companies and individuals.
I think it's ok to plug my own project: It's called Starboard [1] and is truly open source [2]. It's built on different principles: it's hackable, extendable, embeddable, shareable, and easy to check into git (i.e. I try to take what makes the web so great and put that in a notebook environment). You write vanilla JS/ES/Python/HTML/CSS, but you can also import your own more advanced cell types. Here's an example which actually introduces an Observable cell type [3] which is built upon the Observable runtime (which is open source) and an unofficial compiler package [4]. I would be happy for the D3 examples to be expressed in these really-close-to-vanilla JS notebooks, but I can convince the maintainers to do so.
[1]: https://starboard.gg
[2]: https://github.com/gzuidhof/starboard-notebook
[3]: https://starboard.gg/gz/open-source-observablehq-nfwK2VA
[4]: https://github.com/asg017/unofficial-observablehq-compiler
-
Prior to version v0.11.0, Clio used JSON for serialization. JSON is available everywhere and it’s fairly fast, so at first, it might sound like a good idea to go with JSON. Unfortunately, as soon as we start serializing custom types with JSON, its performance degrades to the point that it’s not efficient anymore. To solve this issue, I created a serialization library for JavaScript named Sia, and to boost its serialization performance to the next level, I also designed a new text encoding which I called utfz. I spent over a year optimizing these two libraries, and as a result, managed to make Sia so fast that the pure JavaScript version of it beats even the performance of the native serialization libraries available for Node.js!
JavaScript Compiler related posts
Index
What are some of the best open-source Compiler projects in JavaScript? This list will help you:
| Project | Stars | |
|---|---|---|
| 1 | Next.js | 77,569 |
| 2 | webpack | 59,863 |
| 3 | Gatsby | 51,821 |
| 4 | parcel | 39,560 |
| 5 | marked | 26,434 |
| 6 | pkg | 19,208 |
| 7 | compiler-explorer | 9,759 |
| 8 | Lebab | 5,477 |
| 9 | bytenode | 1,556 |
| 10 | pyret-lang | 881 |
| 11 | clio | 871 |
| 12 | webassemblyjs | 626 |
| 13 | sablejs | 524 |
| 14 | hyper-haskell-server | 356 |
| 15 | BQN | 319 |
| 16 | Duckuino | 276 |
| 17 | tasmocompiler | 214 |
| 18 | Appfairy | 209 |
| 19 | serverless-layers | 158 |
| 20 | mcscript | 153 |
| 21 | DataFormsJS | 117 |
| 22 | unofficial-observablehq-compiler | 80 |
| 23 | sia | 36 |
Are you hiring? Post a new remote job listing for free.
