Fable.Lit
import-maps
Fable.Lit | import-maps | |
---|---|---|
9 | 45 | |
83 | 2,634 | |
- | 1.0% | |
0.0 | 3.1 | |
about 1 year ago | 6 months ago | |
F# | JavaScript | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Fable.Lit
-
How do I understand the build system in modern F# web projects?
The other major frameworks I use are tailwindcss for styling and Fable.Lit for the views.
-
What do people use for REST APIs and Web Development now?
Lit for Lit components.
- [Presentation] Fable.Lit
-
F(#)ront-end Experience like Re-Frame (clojure(script))?
The Feliz DSL https://zaid-ajaj.github.io/Feliz/ looks fairly similar to Reagent or there's Fable.Lit https://fable.io/Fable.Lit/ which is more like jsx in that you write the html directly, adding active components via interpolated string mechanisms. There is a VS Code add in that gives you html+css syntax highlighting and auto complete inside your F# files.
-
Exploring The F# Frontend Landscape
This is my personal favorite one when it comes to Fable options, Fable.Lit builds on top of lit.dev which is a web component library built on web standards. It brings performant straightforward and inter-framework compatible components to the F# FE landscape since Lit works with DOM elements themselves rather than abstractions you can manipulate component instances like if you were doing vanilla JavaScript except that you can use the F# safety for that.
-
Building a Webpack alternative in F#
Around September vite got traction with the vue user base and other users as well. I also studied a bit the vite source code, and even used it for some Fable material for posts. I was trying to make some awareness of Fable.Lit support for Web Components and I wanted to experiment in reality how good vite was, and boi it's awesome If you're starting new projects that depend on node tooling in my opinion, it's your best bet.
-
Fable is a compiler that brings F# into the JavaScript ecosystem
I don't know a ton about Fable, but they recently wrapped Google's Lit to allow building functional templating and web components in it: https://fable.io/Fable.Lit/
Seems like a neat project.
-
Creating Web Components with Fable.Lit
Try Lit.Fable today!
-
Using lit-html with F#
Check the fable.lit github repository to see also ways to interact with inter-operate Lit + React within Fable!
import-maps
-
It is hard to avoid JavaScript
Long time huge fan of JS. I appreciate your calling out the multi-paradigm aspect; having these first class functions & prototype based inheritance has been so flexible.
TC39 has done a great job shaping the language over the years. New capabilities are usually well thought out & integrate well. Async await has been amazing.
The one major miss that makes me so sad and frustrated is modules; js has gotten better everywhere except it's near requirement for build tooling. Being able to throw some scripts on a page and go is still an unparalleled experience in the world, is so direct & tactile an experience. EcmaScript Modules was supposed to improve things, help get us back, but imports using url specifiers made the whole thing non-modular, was a miss. We're still tangled & torn. Import-maps has finally fixed but it's no where near as straightforward, and it still doesn't work in workers, which leaves us infuriatingly shirt of where the past was. https://github.com/WICG/import-maps/issues/2
-
'Mother of all breaches' data leak reveals 26B account stolen records
makes sure your app is getting the download it expects. Adoption is probably pretty minimal though. https://developer.mozilla.org/en-US/docs/Web/Security/Subres...
I think the big thing making this unlikely though is that very few folks use cdns these days. We designed ESM as a module system for the language, but then took a good fraction of a decade to build import-maps, to let us actually use modules in a modular way. Good news, we can finally use modules modularly! https://caniuse.com/import-maps
Bad news? Oh import-maps only works for the simplest case. Doesn't work in webworkers/service workers. https://github.com/WICG/import-maps/issues/2
The point is that single page apps almost always are bundled together, as using CDNs hasn't even been technically possible.
Also, CDNs are kind of somewhat pointless, now that http caches are partitioned by origin (for security reasons). They might have better anycast infrastructure to get the content out faster, but without the caching there's no inherent advantage. The user will download the same jquery file again in each site they go to, no already having it cached anymore. Bah humbug!
- Rails Frontend Bundling - Which one should I choose?
- ESM dynamic imports
-
JavaScript import maps are now supported cross-browser
https://github.com/WICG/import-maps/issues/2
-
We Added Package.json Support to Deno
Bare specifiers has been the tragedy of ESM. Nice module syntax... that is utterly u deoyable & which has had to have awful de-modularizing specifiers hard-coded into each file to make it work. Abominable sin to introduce "modules" to JS/es2015 then spend a decade dragging everyone along with no story for how to have modular modules.
Import-maps are like "here" to fix this on the web... finally... except they only are shipping to the happiest sunniest easiest case, with Web Workers being totally shit out of luck in spite of some very simple straightforward suggested paths forward. https://github.com/WICG/import-maps/issues/2
I think Deno is making pretty good tradeoffs along the way here. This looks like package.json at surface level, but there is a nightmare of complexity under the surface. Typescript, ESM, cjs all have various pressures they create & in Node it's just incredibly tight & tense dealing with packaging, where-as Deno's happy path of Typescript first does not slowly tatters one over time. It really has been super pleasant being free of the previous world, and having something much more web-platform centric, more intented, with less assembly & less building, and more doing the actual coding.
I really hope import-maps eventually get broader support. Maybe this long-dwelling webworker issue should be brought up with WinterCG.
-
Import maps 101
Import maps proposal
-
You Might Not Need Module Federation: Orchestrate your Microfrontends at Runtime with Import Maps
The concept of Import Maps was born in 2018 and made its long way until it was declared a new web standard implemented by Chrome in 2021 and some other browsers.
-
Getting an "import file" syntax right for ArkScript
For package managers, you can use something like import maps to let the user specify which path points to what package, and resolve it properly.
-
Deno 1.28: Featuring 1.3M New Modules
Huh. I was about to complain that this breaks with web standards, but apparently it's being proposed as a standard feature: https://github.com/WICG/import-maps
Interesting!
What are some alternatives?
vite - Next generation frontend tooling. It's fast!
esbuild - An extremely fast bundler for the web
Feliz - A fresh retake of the React API in Fable and a collection of high-quality components to build React applications in F#, optimized for happiness
es-module-shims - Shims for new ES modules features on top of the basic modules support in browsers
fast - The adaptive interface system for modern web experiences.
importmap-rails - Use ESM with importmap to manage modern JavaScript in Rails without transpiling or bundling.
Fable: F# |> BABEL - F# to JavaScript, TypeScript, Python, Rust and Dart Compiler
esm.sh - A fast, smart, & global CDN for modern(es2015+) web development.
React - The library for web and native user interfaces.
single-spa - The router for easy microfrontends
fable-react - Fable bindings and helpers for React and React Native
deno - A modern runtime for JavaScript and TypeScript.