proposal-import-attributes
jsbundling-rails
proposal-import-attributes | jsbundling-rails | |
---|---|---|
9 | 38 | |
555 | 806 | |
2.0% | 1.0% | |
5.9 | 6.5 | |
5 months ago | 20 days ago | |
HTML | Ruby | |
Apache License 2.0 | 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.
proposal-import-attributes
-
The long path of JavaScript - from ES6 until today.
The proposal for import attributes aims to improve the import statement in JavaScript by allowing developers to assert certain conditions about the imported module. This can help catch errors at compile-time instead of runtime and make the code more robust. Currently this proposal is in Stage 3.
-
Power of Partial Prerendering with Bun
Bun introduces the idea of Macros into JavaScript. Macros are a new paradigm that allows optimizations ahead of time just by adding an import attribute.
-
How to use import attributes in TypeScript and JavaScript
TypeScript v5.3 builds on its JavaScript foundation by adding import attributes with the usual type safety and tooling benefits inherent to the language. You can follow the TypeScript proposal for import attributes on GitHub.
-
CSS Modules Still a Thing?
Yup, in vanilla that's fine, but I'm not sure whether bundlers etc are able to understand import assertions yet, as the spec is still being finalised - for example: the 'assert' keyword has now been officially changed to 'with', but only 'assert' is implemented anywhere at the moment.
-
If Web Components are so great, why am I not using them?
Things like HTML (and JSON) imports in ES modules, among other things, have been waiting on some safety signalling mechanics currently named "Import Attributes". Import Attributes are currently in Stage 3 [0].
The basic security story is that browsers never care about file extensions, they care about MIME types. A developer might add an import to a third-party HTML or JSON file somewhere and expect one "safe" behavior, but the third-party could just return a MIME type of "text/javascript" and inject an entire script and the browser is supposed to respect that MIME type.
To keep things safe, browsers want a way to signal that an import is supposed to JSON (or HTML or CSS) rather than JS and error if it gets back something "wrong" from a server request. That's one of the proposed uses for Import Attributes to suggest expected MIME types for non-JS modules in ES module imports.
Unfortunately, there are other proposed uses for Import Attributes (things like including hashes for integrity checks) and so there have been quite a few revisions (and multiple names) for Import Attributes trying to best support as many of the proposed uses as possible, and that has slowed progress on it a lot more than some people would wish.
[0] https://github.com/tc39/proposal-import-attributes
-
[Showoff Saturday] Replacing Abandoned Dependencies
This was an idea that I came up with when thinking about how to handle import styles from './styles.css' with { type: 'css' } in @shgysk8zer0/rollup-import. Import assertions / import attributes are now back to stage 3, but only JSON is actually progressing. So I decided to wait until there's a stable spec.
- Rails Frontend Bundling - Which one should I choose?
-
The Cost of Convenience
None of these examples will actually work in a browser, because they are non-standard. Some of you might have correctly spotted that a browser standard exists for two of the imports pointed out in the example, namely the Import Attributes proposal (previously known as Import Assertions), but these imports in their current shape will not work natively in a browser. Many of these non-standard imports exist for good reason; they are very convenient.
-
Updates from the 95th TC39 meeting
import attribute: Import Assertions re-adanced to Stage-3. Proposal for syntax to import ES modules with assertions
jsbundling-rails
- Rails Merging Support for Bun.sh
- Rails Frontend Bundling - Which one should I choose?
-
Is the default importmap method unrealistic in the most popular real world use cases?
I think this is more like a demo - you will not get the same features as jsbundling-rails by only following instructions in the video. For that you will need to change some other files as well. You can find out what files to be added/changed from the install script. The important bits are mostly the same as in the video, but some supplement parts are not mentioned in the video. Some people actually reported in the comment that they can't deploy such app, but I think it depends.
-
at my wits' end.. please help me figure out why javascript won't work (Rails 7 with esbuild)
I'm sorry, I didn't see that in your title. Using esbuild is 100% supported by Rails through this gem https://github.com/rails/jsbundling-rails. Have a look at the docs there to make sure that you're setup correctly.
-
Configure Stimulus with esbuild and Babel — Rails & Javascript
Rails applications are bundler-agnostic. They do not care how you bundle your javascript code. It just expects whatever comes from the bundler to be placed under app/assets, so the asset pipeline processes it. We can see this in the official jsbundling-rails gem, which consists of scripts to install different bundlers and configure a default npm build command to generate our bundles—no interaction whatsoever with the Rails configuration. This black-box bundler logic allows us to change and update our bundler system without tuning any other aspect of our Rails application.
-
foreman: not found
Hello, this is my first time setting up a rails app that also uses react, I am using https://github.com/rails/jsbundling-rails I went with esbuild because I am following this tutorial on setting it up https://www.youtube.com/watch?v=yoLJXjEV2nM, however when I run bin/dev in the terminal I get the error bin/dev: 8: exec: foreman: not found
- Ruby 3.2 + Rails 7 + Tailwind + Font Awesome - should be blazing fast, yet tests very slow. 20 requests are being made. How do I make fewer requests, create fewer objects and make this simple app super fast? Production : https pickaxe dot ca. Thank you! -Dan H
-
How to bundle assets in a Rails engine
You first install your asset handlers as you need them for your project. They can be anything from rails/jsbundling-rails and rails/tailwindcss-rails to webpacker or something custom.
-
Comparing Phoenix to Rails in December 2022
The functionality comes from https://github.com/rails/jsbundling-rails and https://github.com/rails/cssbundling-rails -- both come with Rails 7 and all you have to do is generate your app with the choices you want such as -j esbuild --css tailwind.
-
Vercel announces Turbopack, the successor to Webpack
The Rails https://github.com/rails/jsbundling-rails gem lets you pick between esbuild, rollup and Webpack. If Turbopack ends up being popular then jsbundling should be able to support it.
The nice thing about Rails now is there's no direct integration like Webpacker once was. Now we can basically use the JS tool straight up and Rails will just look at assets in a specific directory, it doesn't matter what tool generated it.
What are some alternatives?
proposal-class-method-parameter-decorators - Decorators for ECMAScript class method and constructor parameters
importmap-rails - Use ESM with importmap to manage modern JavaScript in Rails without transpiling or bundling.
unpkg - The CDN for everything on npm
vite_ruby - ⚡️ Vite.js in Ruby, bringing joy to your JavaScript experience
proposal-float16array - a proposal to add float16 TypedArrays to JavaScript
hotwire-rails - Use Hotwire in your Ruby on Rails app
proposal-await-dictionary - A proposal to add Promise.ownProperties(), Promise.fromEntries() to ECMAScript
esbuild-live-reload
uibuilder - Typed HTML templates using TypeScript's TSX files
Webpacker - Use Webpack to manage app-like JavaScript modules in Rails
custom-elements - Using custom elements
esbuild - An extremely fast bundler for the web