svelte-on-rails 1.0.0 → 1.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +5 -8
  3. metadata +3 -2
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: af9b4125161ea52c5785989db9e7f4b250a4bbe993f49264403680c5aa5467fb
4
- data.tar.gz: 1d21a733aa52d57f892159baeb88c162cb78f46fca648dd2f31b45e3db8819e0
3
+ metadata.gz: af8d4bb8fb9c9601a9aaf54fedf5e7f419ce3320b1f729fd35032e10fe3486cf
4
+ data.tar.gz: 6fea536491f0493e574a0432a7a2b9f2bbf2d28b8e0dab806585695da011d212
5
5
  SHA512:
6
- metadata.gz: 72c0797453be3020409b6e28f5b7f472e8e0c1a22e010c401925ad2a81ac360c522612a7e52bac3d7a8da5a4c51f62668a68d46a33b3a955ed9e072366a567fd
7
- data.tar.gz: 7f377d2c359daa8a9a2e18cd7c147187dd4249bbd0a8b5987f0feddb4a7b72020bc49591e04502055e4a7223e78e05b8e832c21c345dc93ac1d943440587dfc0
6
+ metadata.gz: ec46124593dc6d40cf8ea051872746bc7070d9e2adec974c1ca7910645030e6324c5f7a280264cef4289dd99fdf60b1dd201291bae55e2aea01189bf5d6ec2fa
7
+ data.tar.gz: c7f5a5a822fc1e1f5cb961dcd4158808fdcc1ee8303ba5e2fc0d4a0c52f50cd4abe1fa8b426ea43798bdc4daa777b6fd3165c2f65057471a504fbc46cbba34d9
data/README.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # Svelte on Rails
2
2
 
3
- Seamless and robust Svelte in Rails integration.
3
+ Rock-solid and seamless integration of Svelte Components into Rails views, based on `vite_rails`.
4
4
 
5
5
  By default, and when installed together with `@hotwired/turbo-rails`, it renders
6
6
  svelte components on the first request server side («SSR») and for subsequent
@@ -11,8 +11,6 @@ This way svelte works perfectly together with turbo. You will never notice
11
11
  this unpleasant «blink» on the frontend and is optimised for maximum
12
12
  performance. SSR compilation is done by vite.
13
13
 
14
- All this is developed on Rails-7 together with `vite_rails`.
15
-
16
14
  Thanks to [shakacode](https://github.com/shakacode/react_on_rails)
17
15
  and [ElMassimo](https://github.com/ElMassimo) for inspiring and helping me with their gems.
18
16
 
@@ -20,7 +18,7 @@ and [ElMassimo](https://github.com/ElMassimo) for inspiring and helping me with
20
18
  It has a 100% test coverage, all tests pass.
21
19
  It is not yet implemented on my customer projects, but this will follow soon.
22
20
 
23
- If you have issues, please open one and contributors are welcome!
21
+ If you have issues, please open one, and contributors are welcome!
24
22
 
25
23
  ## Requirements
26
24
 
@@ -203,8 +201,7 @@ rake svelte_on_rails:create_contributor_configs_file
203
201
  and define a `generated_test_app_folder_path` (required) for apps, generated for the testings.
204
202
 
205
203
  For development of the **npm package @csedl/svelte-on-rails** (optional) please download the source code of the
206
- npm package and set
207
- `local_npm_package_path` and set the path to the npm package on your local machine.
204
+ npm package and set `local_npm_package_path` on the config file to the path to the npm package on your local machine.
208
205
  This will cause the installer, to install the npm package from a local path instead from the npm registry.
209
206
 
210
207
  Then run the tests and start contributing.
@@ -249,9 +246,9 @@ side could live on the same assets and manifest like svelte components that are
249
246
  compiled as chunks which each is its own entry point. This failed:
250
247
 
251
248
  - The `vite-plugin-ruby` did not support this: it constrained all to one entry point.
252
- - See how fat the `vite-ssr.config.ts`. For the client side this is not necessary.
249
+ - See how fat the `vite-ssr.config.ts` is. For the client side this is not necessary.
253
250
 
254
- At the end, I decided to split the process. But that is not the last decision.
251
+ At the end, I decided to split the process. For now it is cleaner. But that is not the last decision.
255
252
 
256
253
  **Why not compiling server side purely by rollup?**
257
254
 
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: svelte-on-rails
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.0.0
4
+ version: 1.0.2
5
5
  platform: ruby
6
6
  authors:
7
7
  - Christian Sedlmair
@@ -95,5 +95,6 @@ required_rubygems_version: !ruby/object:Gem::Requirement
95
95
  requirements: []
96
96
  rubygems_version: 3.6.7
97
97
  specification_version: 4
98
- summary: Seamlessly integrate Svelte Components into Rails views.
98
+ summary: Rock-solid and seamless integration of Svelte Components into Rails views,
99
+ based on vite_rails.
99
100
  test_files: []