svelte-on-rails 1.0.1 → 1.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: bc4a6377868a5a06f7160c6e9a543ce94fbff469a3152051a9ac4091f37e3659
-  data.tar.gz: 2b451e6217380df53a0f1163347e320ea932386c6ba794916dd2edc07e2de037
+  metadata.gz: af8d4bb8fb9c9601a9aaf54fedf5e7f419ce3320b1f729fd35032e10fe3486cf
+  data.tar.gz: 6fea536491f0493e574a0432a7a2b9f2bbf2d28b8e0dab806585695da011d212
 SHA512:
-  metadata.gz: 1bc7158bcec98b8566f280e8f2034d58d3f1bc64257ac7a54919c3e7247e8068ac282fabfdfa370422cd61173d780ef62be130b38dab290b5f73d8a050807723
-  data.tar.gz: 2504cdf6ada8a93a69dd67bd9b56fb54f1d6260d909ec91437b08df16af705700425194fd65ad56f83a990427b023b52f3cc8ed03421a0bda1b0622332454b68
+  metadata.gz: ec46124593dc6d40cf8ea051872746bc7070d9e2adec974c1ca7910645030e6324c5f7a280264cef4289dd99fdf60b1dd201291bae55e2aea01189bf5d6ec2fa
+  data.tar.gz: c7f5a5a822fc1e1f5cb961dcd4158808fdcc1ee8303ba5e2fc0d4a0c52f50cd4abe1fa8b426ea43798bdc4daa777b6fd3165c2f65057471a504fbc46cbba34d9

data/README.md

@@ -1,6 +1,6 @@
 # Svelte on Rails
 
-Seamless and rock-solid integration of Svelte Components into Rails views, based on `vite_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 +18,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 +201,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 +246,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?**
 

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.2
 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: []