Rust Language Server
es-module-shims
Our great sponsors
Rust Language Server | es-module-shims | |
---|---|---|
6 | 13 | |
3,568 | 1,479 | |
- | - | |
7.0 | 6.3 | |
over 1 year ago | 22 days ago | |
Rust | JavaScript | |
GNU General Public License v3.0 or later | MIT License |
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.
Rust Language Server
-
Why doesn't rust-analyzer reuse infrastructures of rustc?
In the last there was RLS that did exactly that. But the approach of rust-analyzer was found to be more performant.
-
[RFC] Generate Cabal files from TOML
LSP support seems to be lacking as well, at least rust doesn't seem to have Cargo.toml support? https://github.com/rust-lang/rls/issues/785
-
Referencing files in subfolders and difference between borrowing and C like references
apparently, it means that you're using the old RLS-based Rust plugin for VS Code, rather than the rust-analyzer plugin. You probably won't see a lot of people familiar with RLS's error messages.
-
friendly reminder for our vscode folks, use rust-analyzer
Why: The rust-analyzer extension integrates with rust-analyzer, an alternative language server for Rust. rust-analyzer tends to perform better and get less confused with your code as compared to RLS, which the Rust extension uses.
-
Show HN: Skruv – No-dependency, no-build, small JavaScript framework
I have tried writing websites with rust instead of JavaScript. Unfortunately, the tooling is just not there. More specifically, I am talking about wasm-bindgen, which provides two-way bindings. The problem with it is that since all the declarations are generated with build.rs, there is no autocompletion. Since I am spoiled by modern tooling, no autocompletion to me means not feasible pass demo stage. (https://github.com/rust-lang/rls/issues/1489)
Aside from the lack of autocompletion, passing rust closures to js land (DOM) is extremely janky as well. However, that might be caused by my lack of experience with rust.
(If you are curious, this is what I made: https://github.com/SCLeoX/non-grid-path-finder)
-
José Valim The Creator Of The Elixir Programming
Python the core devs don't care about tooling and they have IDE's, Java is an enterprise monolith so IDE's are the standard, Rust yes it is (https://github.com/rust-lang/rls), Elm I have no idea I don't use it.
es-module-shims
-
⏰ It’s time to talk about Import Map, Micro Frontend, and Nx Monorepo
For full compatibility and extra features, we usually use the library es-module-shims.
-
JavaScript import maps are now supported cross-browser
You can polyfill for unsupported browsers, it works surprisingly well: https://github.com/guybedford/es-module-shims
-
Modern SPAs without bundlers, CDNs, or Node.js
https://github.com/guybedford/es-module-shims has a polyfill. (But it is fairly large: 53KB raw, 15KB gzipped, 32KB minified, 11KB minified+gzipped. It’s providing a lot of likely-unnecessary functionality. I’d prefer a stripped-down polyfill that can also be lazily-loaded, controlled by a snippet of at most a few hundred bytes that you can drop into the document, only loading the polyfill in the uncommon case that it’s needed—like how five years ago as part of modernising some of the code of Fastmail’s webmail, I had it fetch and execute core-js before loading the rest iff !Object.values (choosing that as a convenient baseline), so that the cost to new browsers of supporting old browsers was a single trivial branch, and maybe fifty bytes in added payload.)
- Writing JavaScript without a build system
-
Modern SPAs without bundlers, CDNs, or NodeJS
If we call the shim a framework, would you be ok with it then?
-
Import maps 101
If you want import maps to be supported in any browser, there is an ES Module Shims polyfill which is compatible with any browser that has baseline ES Module Support (i.e. Edge 17+, Firefox 60+, Safari 10.1+, and Chrome 61+).
-
Everything You Need to Know About JavaScript Import Maps
An example of a polyfill that can be used is the ES Module Shims polyfill that adds support for import maps and other new module features to any browser with baseline support for ES modules (about 94% of browsers). All you need to do is include the es-module-shim script in your HTML file before your import map script:
-
How bad is it to not use a bundler?
i often use es-module-shims so i can load npm packages in browsers without a bundler 😎
-
Fresh – The next-gen web framework
I explored using client-side service workers for build-less deployment workflows a while back, but the blocker was the initial visit when the service worker hasn't been installed yet. Ended up using es-module-shim's fetch hook (https://github.com/guybedford/es-module-shims#fetch-hook) instead, which worked quite well.
I kept the demo repo around here, in case it's helpful to anyone: https://github.com/lewisl9029/buildless-hot-reload-demo.
The repo itself is quite out of date at this point, but my current project, Reflame, is essentially the spiritual successor: https://reflame.app/
Reflame has the same ideals of achieving the developer experience I've always wanted for building client rendered React apps:
- instant production deployments (usually <200ms)
- instant preview environments that match production in pretty much every imaginable way (including the URL), that can also be flipped into development mode for fast-refresh (for the seamless feedback loop we're used to in local dev) and dev-mode dependencies (for better error messaging, etc)
- close-to-instant browser tests (1-3 seconds) that enable image snapshot comparisons that run with maximum parallelism and only rerun when their dependency graphs change
-
Do you use Import-Map for your client-side ESM?
The problem of course is that browser-support for Import Maps is sadly lacking (only Chrome/Chromium-based at time of writing). There are tricks/shims to get around this, like ES-Module-Shims. I find these approaches to be a little too intrusive, personally.
What are some alternatives?
Rustup - The Rust toolchain installer
import-maps - How to control the behavior of JavaScript imports
Racer - Rust Code Completion utility
hyperscript - Create HyperText with JavaScript.
rusty-tags - Create ctags/etags for a cargo project
stampino-element
rust-analyzer - A Rust compiler front-end for IDEs
import-remap - Rewrite ES module import specifiers using an import-map.
semantic-rs
mercury - A truly modular frontend framework
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
codesandbox-client - An online IDE for rapid web development