proscenium 0.19.0.beta20-x86_64-linux → 0.19.0-x86_64-linux

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: ecfaf29ea947161d09ad984b294db2f828d49b711ec179642bd8653760225135
-  data.tar.gz: '08ce77173b0e4b1fa1f204a3c537bd4f59746837e0960b054ecde6547b7571ef'
+  metadata.gz: e686c9d55f815ad70fc17be7ad98bde1bfaf57dd426464a75fda4b3f08fd3d9d
+  data.tar.gz: 362e72b47cdcb0743cff1ab94e3cc413f2b85e605225fbc2706342760958133a
 SHA512:
-  metadata.gz: 92196d7abd932d44ec0b50f76539b4d2c3ff9406fe0bacd52f324826d99396ea46d4c14fa2e3e07eb75cd9d6fa5103caae6858c7bf32c8fd2991710034e35d4f
-  data.tar.gz: ae2ebc5a11d2b975495a351ceb0efc13c7c1f0d4cf49ca66406b106a6d3cdd692e9b406f67f4459a362347387122de06105083ef7ce57f017461dee17144f9fe
+  metadata.gz: 17a945e83e1e18faff56b408ef10245dec73b7baea589f41fc5125d7febb89f88463c09b2a868889ee8275879961b2e04cf3b9ef6c6632f1612504aa7d4aa2ae
+  data.tar.gz: 889ed2b063887281c9aa1e51c28f5c7aad1bc8f400bf5090e7121b0fc6718c9e4584b9c5d5320a99a8029c4cccd1255fffaefa761f648920d879ea45463c390d

data/README.md

@@ -6,17 +6,17 @@
 >
 > - _the part of a theatre stage in front of the curtain._
 
-**_Proscenium_** treats your frontend and client-side code as first class citizens of your Rails app, and assumes a "fast by default" internet. It bundles and minifies JavaScript (+ JSX), TypeScript (+TSX) and CSS in real time, on demand, and with zero configuration.
+**_Proscenium_** treats your frontend and client-side code as first class citizens of your Rails app, and assumes a "fast by default" internet. It bundles and minifies JavaScript (+JSX), TypeScript (+TSX) and CSS in real time, on demand, and with zero configuration.
 
 **The highlights:**
 
 - Fast, real-time bundling, tree-shaking, code-splitting and minification of Javascript (.js,.jsx), Typescript (.ts,.tsx) and CSS (.css).
 - NO JavaScript runtime needed (eg. Node) - just the browser!
 - NO build step or pre-compilation.
-- NO additional process or server - Just run `rails s`!
+- NO additional process or server - Just run `rails server`!
 - Transforms newer JavaScript and CSS syntax to older syntax for older browsers.
 - Deep integration with Rails.
-- Automatically side-load your layouts, views, and partials.
+- Automatically side-load JS and CSS for your layouts, views, and partials.
 - Import from NPM, URL's, and locally.
 - Server-side import map support.
 - CSS Modules & mixins.
@@ -75,15 +75,15 @@ gem 'proscenium'
 
 Please note that Proscenium is designed solely for use with Rails.
 
-Now if you start your Rails app, you can open any front end code (JS, CSS, etc.). For example, a file at `app/assets/stylesheets/application.css` can be accessed at `https://localhost:3000/app/assets/stylesheets/application.css`, which will be bundled, transformed, and minified [in production] in real time.
+Now if you start your Rails app, you can open any front end code (JS, CSS, etc.). For example, a file at `app/assets/stylesheets/application.css` can be accessed at `https://localhost:3000/app/assets/stylesheets/application.css`, which will be transformed, bundled, and minified [in production] in real time.
 
 ## Client-Side Code Anywhere
 
-Proscenium believes that your frontend code is just as important as your backend code, and is not an afterthought - they should be first class citizens of your Rails app. So instead of having to throw all your JS and CSS into a "app/assets" directory, and then requiring a separate process to compile or bundle, just put them wherever you want within your app, and just run Rails!
+Proscenium believes that your frontend code is just as important as your backend code, and is not an afterthought - they should be first class citizens of your Rails app. So instead of having to throw all your JS and CSS into a "app/assets" directory, and then requiring a separate process to compile or bundle, you can simply put them wherever you want within your app, and just run Rails!
 
 For example, if you have some JS that is required by your `app/views/users/index.html.erb` view, just create a JS file alongside it at `app/views/users/index.js`. Or if you have some CSS that is used by your entire application, put it in `app/views/layouts/application.css` and load it alongside your layout. Maybe you have a few JS utility functions, so put them in `lib/utils.js`.
 
-Simply put your JS(X) and CSS anywhere you want, and they will be served by your Rails app from the location where you placed them.
+Simply put your JS(X) and CSS anywhere you want, and they will be served by your Rails app from the same location where you placed them.
 
 Using the examples above...
 
@@ -95,15 +95,15 @@ Using the examples above...
 
 ## Side Loading
 
-Proscenium is best experienced when your assets are automtically side loaded.
+Proscenium is best experienced when your assets are automatically side loaded.
 
 ### The Problem
 
-With Rails you would typically declaratively load your JavaScript and CSS assets using the `javascript_include_tag` and `stylesheet_link_tag` helpers.
+With Rails you would typically load your JavaScript and CSS assets declaratively using the `javascript_include_tag` and `stylesheet_link_tag` helpers.
 
-For example, you may have top-level "application" CSS located in a file at `/app/assets/stylesheets/application.css`. Likewise, you may have some global JavaScript located in a file at `/app/javascript/application.js`.
+For example, you may have top-level "application" styles located in a file at `/app/assets/stylesheets/application.css`. Likewise, you may have some global JavaScript located in a file at `/app/javascript/application.js`.
 
-You would manually and declaratively include those two files in your application layout, something like this:
+You would manually and declaratively include those two files in each of your layouts, something like this:
 
 ```erb
 <%# /app/views/layouts/application.html.erb %>
@@ -141,7 +141,9 @@ The main problem is that you have to keep track of all these assets, and make su
 
 When side loading your JavaScript, Typescript and CSS with Proscenium, they are automatically included alongside your views, partials, layouts, and components, and only when needed.
 
-Side loading works by looking for a JS/TS/CSS file with the same name as your view, partial, layout or component. For example, if you have a view at `app/views/users/index.html.erb`, then Proscenium will look for a JS/TS/CSS file at `app/views/users/index.js`, `app/views/users/index.ts` or `app/views/users/index.css`. If it finds one, it will include it in the HTML for that view.
+Side loading works by looking for a JS/TS/CSS file with the same name as your view, partial, layout or component. For example, if you have a view at `app/views/users/index.html.erb`, then Proscenium will look for a JS and CSS file at `app/views/users/index.js` (or TypeScript with a .ts extension) and `app/views/users/index.css`. If it finds one, it will automatically include it in the HTML for that view. And only for that view.
+
+This allows you to keep your assets organized alongside the views, partials, and components that use them, without having to manually track and include them. It also means only the assets that are needed are included.
 
 JSX is also supported for JavaScript and Typescript. Simply use the `.jsx` or `.tsx` extension instead of `.js` or `.ts`.
 
@@ -272,6 +274,14 @@ Then just import as normal:
 import React from "react";
 ```
 
+Or if you don't want any bundling at all, simply turn it off application-wide:
+
+```ruby
+config.proscenium.bundle = false
+```
+
+This will mean every asset and import will be loaded independently.
+
 ## Import Maps
 
 > **[WIP]**
@@ -441,8 +451,6 @@ one();
 
 ### Code Splitting
 
-> Available in `>=0.10.0`.
-
 [Side loaded](#side-loading) assets are automatically code split. This means that if you have a file that is imported and used imported several times, and by different files, it will be split off into a separate file.
 
 As an example:
@@ -682,8 +690,6 @@ console.log(version);
 
 ## Cache Busting
 
-> _COMING SOON_
-
 By default, all assets are not cached by the browser. But if in production, you populate the `REVISION` env variable, all CSS and JS URL's will be appended with its value as a query string, and the `Cache-Control` response header will be set to `public` and a max-age of 30 days.
 
 For example, if you set `REVISION=v1`, URL's will be appended with `?v1`: `/my/imported/file.js?v1`.

data/lib/proscenium/builder.rb

@@ -16,6 +16,7 @@ module Proscenium
 
     module Request
       extend FFI::Library
+
       ffi_lib Pathname.new(__dir__).join('ext/proscenium').to_s
 
       enum :environment, [:development, 1, :test, :production]

data/lib/proscenium/css_module/transformer.rb

@@ -70,7 +70,7 @@ module Proscenium
       digest = Importer.import(resolved_path)
 
       transformed_path = ''
-      transformed_path = "__#{resolved_path[1..].gsub(%r{[@/\.+]}, '-')}" if Rails.env.development?
+      transformed_path = "__#{resolved_path[1..].gsub(%r{[@/.+]}, '-')}" if Rails.env.development?
       transformed_name = name.to_s
       transformed_name = if transformed_name.start_with?('_')
                            "_#{transformed_name[1..]}-#{digest}#{transformed_path}"

data/lib/proscenium/helper.rb

@@ -40,18 +40,6 @@ module Proscenium
                             .map { |name, _| name }.join(' ')
     end
 
-    # @param name [String,Symbol,Array<String,Symbol>]
-    # @param path [Pathname] the path to the CSS file to use for the transformation.
-    # @return [String] the transformed CSS module names concatenated as a string.
-    def class_names(*names, path: nil)
-      names = names.flatten.compact
-
-      return if names.empty?
-
-      path ||= Pathname.new(@lookup_context.find(@virtual_path).identifier).sub_ext('')
-      CssModule::Transformer.new(path).class_names(*names).map { |name, _| name }.join(' ')
-    end
-
     def include_assets
       include_stylesheets + include_javascripts
     end

data/lib/proscenium/side_load.rb

@@ -134,7 +134,7 @@ module Proscenium
         # in the ancestry is also sideloaded in addition to the regular CSS files. This is because
         # the CSS module digest will be different for each file, so we only sideload the first CSS
         # module.
-        css_imports.each do |it|
+        css_imports.each do |it| # rubocop:disable Style/ItAssignment
           break if Importer.sideload_css_module(it, **options).present?
         end
 
@@ -143,7 +143,7 @@ module Proscenium
         # The reason why we sideload CSS after JS is because the order of CSS is important.
         # Basically, the layout should be loaded before the view so that CSS cascading works in the
         # right direction.
-        css_imports.reverse_each do |it|
+        css_imports.reverse_each do |it| # rubocop:disable Style/ItAssignment
           Importer.sideload_css it, **options
         end
       end

data/lib/proscenium/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Proscenium
-  VERSION = '0.19.0.beta20'
+  VERSION = '0.19.0'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: proscenium
 version: !ruby/object:Gem::Version
-  version: 0.19.0.beta20
+  version: 0.19.0
 platform: x86_64-linux
 authors:
 - Joel Moss
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2025-07-22 00:00:00.000000000 Z
+date: 2025-09-08 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: ffi