svelte-on-rails 1.0.12 → 1.0.13

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 89b585de2264458769d479f27bcadc4080a8984b23e916cccd5d07876a30ea24
-  data.tar.gz: 7255f6af6ee943e809b24ba6551730e05dd21b8279555c677f7be2346d47a0f1
+  metadata.gz: c2bddaae521fc71ed3c7975612b8b9109830fd25210eda2d30c00c6150265dca
+  data.tar.gz: 7adeb7e7181508d704ff98087f5b601a596159d1205cb0ffb08e98f5fca81272
 SHA512:
-  metadata.gz: 3557343363ea9f1776a6766eadcb97a3d8e6376ac069b1daa764cd77aa87a2f04614c91f3ed0b9d16a549b4ca7651ad82716d4b2374fc222c6d649d1e1c538c3
-  data.tar.gz: 4f301fb16a422e682e75ca9ebf09a207474346ff973140191d8e92226bc9b284c04eaa3c3662f6745b83637b6db83752c8b5b4dcfa35deaec71eaa0d0ad1d973
+  metadata.gz: 77f1fd03901c9c73c8893c471b464db9e2e4fd212b9a36dad9a78f15b34f155865155b4796af3409e32b741dd4693a9756c369bcfb32caf05b1a1abdfa6e1af5
+  data.tar.gz: 7be8fd8640a3d7431dd6e8274a3bc3f3a9eca0c9c9e30f46d42f4eb00735f13a8e8421e8b0e6142c17ac0a0aab9bc9df5cc0914b17add50677498575401ac20b

data/README.md

@@ -4,7 +4,14 @@
 
 ---
 
-Svelte is the missing peace for ambitious Rails frontends.
+Do you want to combine DHH's [vision](https://rubyonrails.org/2021/12/15/Rails-7-fulfilling-a-vision) 
+with modern front-end requirements?
+
+Svelte.
+
+Vite.
+
+Nothing else.
 
 # Why Svelte? 
 
@@ -14,12 +21,12 @@ On every app there are parts where you want it to shine. This is where Svelte co
 - Perfect addition to Stimulus
 - Easy to learn
 - Powerful
+- Super fast
 - **Compared to Stimulus**
   - No more writing double logic of the initial HTML state
-  - Stimulus is good for parts where you have simple and little javascript and lots of html
-  - The more complexity, the more you will love svelte
+  - Stimulus is great for rails views with some javascript, but, complex parts: Svelte. Nothing else.
 - **Compared to React**
-  - No Shadow dom 
+  - No more shadow dom and all those packages that are supposed to improve performance (e.g. useCallback...)
   - Slimmer packages
   - Easier to learn
   - Faster
@@ -27,12 +34,15 @@ On every app there are parts where you want it to shine. This is where Svelte co
 Have a look at this entertaining video [rethinking reactivity](https://svelte.dev/blog/svelte-3-rethinking-reactivity)
 by Rich Harris, especially from 3:50 to 6:40 and his comparison to react.
 
-This all fits perfectly with the Rails way of minimalist javascript, but: Where we need it, we have it.
+This all fits in perfectly with the Rails way of minimalist javascript,
+but: Where needed, we want full power.
 
 # Features
 
-- 🤝 fully integrated with `assets:precompile`
-- 🚀 cero-config deployment
+- 🤝 Fully integrated with `assets:precompile`
+- 🚀 Cero-config deployment
+- ✍️ Sophisticated error messages
+- 😍 Contributor friendly
 
 # Known Issues
 
@@ -189,7 +199,7 @@ The most importand rule is to firstly check all npm packages installed and passi
 ## Check if it all works
 
 Server Side Rendering (SSR) is a parallel pipeline to client side rendering.
-Both should return the same html. And your global styles should be applied same way
+Both should return the same HTML. And your global styles should be applied same way
 for both cases. For normal use cases this is. 
 
 For check the **ssr pipeline** you can pass the options `ssr: true` and `hydrate: false`

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: svelte-on-rails
 version: !ruby/object:Gem::Version
-  version: 1.0.12
+  version: 1.0.13
 platform: ruby
 authors:
 - Christian Sedlmair
@@ -95,6 +95,5 @@ required_rubygems_version: !ruby/object:Gem::Requirement
 requirements: []
 rubygems_version: 3.6.7
 specification_version: 4
-summary: Rock-solid and seamless integration of Svelte Components into Rails views,
-  based on vite_rails.
+summary: Solid and seamless integration of Svelte Components into Rails views.
 test_files: []