svelte-on-rails 1.0.1 → 1.0.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: bc4a6377868a5a06f7160c6e9a543ce94fbff469a3152051a9ac4091f37e3659
-  data.tar.gz: 2b451e6217380df53a0f1163347e320ea932386c6ba794916dd2edc07e2de037
+  metadata.gz: f2121111d74eaad3c6860fb874a038bc1c45391b87caad1dc183309f078cc3f6
+  data.tar.gz: 9fb8b1e68897f7d058e73c924320e13b3601c70fe37d4077bffbd0e02317544a
 SHA512:
-  metadata.gz: 1bc7158bcec98b8566f280e8f2034d58d3f1bc64257ac7a54919c3e7247e8068ac282fabfdfa370422cd61173d780ef62be130b38dab290b5f73d8a050807723
-  data.tar.gz: 2504cdf6ada8a93a69dd67bd9b56fb54f1d6260d909ec91437b08df16af705700425194fd65ad56f83a990427b023b52f3cc8ed03421a0bda1b0622332454b68
+  metadata.gz: 99e3cd5d5da270bfe4458c05d52ff67e351606c20db9db8423b214ca67b2e49ae00554f5c4226b0117f6583ed079384fbe527f1f0a5031b46fbc6cd640d7439f
+  data.tar.gz: af721320b1380e48eb0c0e4aeec447c419d186a70c0ac25003bb0424cb18d4351241725ed9aee7b6bce7530c7db1b540af931e27ef7d01010f039085fbfcc07b

data/README.md

@@ -1,6 +1,37 @@
-# Svelte on Rails
+<div style="text-align: center;">
+  <img src="./Svelte_Logo.svg.png" alt="Svelte Logo" height="120">
+</div>
 
-Seamless and rock-solid integration of Svelte Components into Rails views, based on `vite_rails`.
+---
+
+Svelte is the missing peace for ambitious Rails applications.
+
+# Why? 
+
+On every app there are parts where you want it to shine. This is where Svelte comes in.
+
+- Works perfectly with Hotwired/Turbo
+- Perfect addition to Stimulus
+- Easy to learn
+- Powerful
+- **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
+- **Compared to React**
+  - No Shadow dom 
+  - Slimmer packages
+  - Easier to learn
+  - Faster
+
+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.
+
+# Svelte on Rails 👍
+
+Rock-solid and seamless integration of Svelte Components into Rails views, based on `vite_rails`.
 
 By default, and when installed together with `@hotwired/turbo-rails`, it renders
 svelte components on the first request server side («SSR») and for subsequent
@@ -18,7 +49,7 @@ and [ElMassimo](https://github.com/ElMassimo) for inspiring and helping me with
 It has a 100% test coverage, all tests pass. 
 It is not yet implemented on my customer projects, but this will follow soon.
 
-If you have issues, please open one and contributors are welcome!
+If you have issues, please open one, and contributors are welcome!
 
 ## Requirements
 
@@ -201,8 +232,7 @@ rake svelte_on_rails:create_contributor_configs_file
 and define a `generated_test_app_folder_path` (required) for apps, generated for the testings.
 
 For development of the **npm package @csedl/svelte-on-rails** (optional) please download the source code of the
-npm package and set
-`local_npm_package_path` and set the path to the npm package on your local machine.
+npm package and set `local_npm_package_path` on the config file to the path to the npm package on your local machine.
 This will cause the installer, to install the npm package from a local path instead from the npm registry.
 
 Then run the tests and start contributing.
@@ -247,9 +277,9 @@ side could live on the same assets and manifest like svelte components that are
 compiled as chunks which each is its own entry point. This failed:
 
 - The `vite-plugin-ruby` did not support this: it constrained all to one entry point.
-- See how fat the `vite-ssr.config.ts`. For the client side this is not necessary.
+- See how fat the `vite-ssr.config.ts` is. For the client side this is not necessary.
 
-At the end, I decided to split the process. But that is not the last decision.
+At the end, I decided to split the process. For now it is cleaner. But that is not the last decision.
 
 **Why not compiling server side purely by rollup?**
 

data/lib/tasks/svelte_on_rails_tasks.rake

@@ -12,7 +12,6 @@ if defined?(Rails) && Rake::Task.task_defined?("assets:precompile")
 end
 
 
-require_relative '../../spec/test_helpers'
 require_relative '../../lib/svelte_on_rails/installer/hello_world'
 require_relative '../../lib/generators/svelte_on_rails/install/install_generator'
 

metadata

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