svelte-on-rails 0.0.10 → 0.0.13

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 91e3a5e36988fe3fd9aa4cbf83c5dd475dae2919dc788afd3e1c3ba399690490
-  data.tar.gz: d9d60ad9b06e29bd1b744575f80bcd2ea9edbe60cc4a1badc6e8178867ff8b36
+  metadata.gz: 60ac9b6c78cf973e7bddd6802c58dc779388e97572087c084870183c773ccf04
+  data.tar.gz: '0529bd1129620c1e5693ca65fbf287e95b055741f5dcc05452645baa3422649d'
 SHA512:
-  metadata.gz: 8e8fa476b10eed4dd4ef9772c60b8e66bdf87fd7627458d9ba301520be94ad7ff96de9ac72ac6cbf85312473cfec42138e94e10110a7647b5a2e412bf460bb2e
-  data.tar.gz: 4539559ff01e47a4138f91cc7258846aa31ca4353b643a8c06dd5995e6cad991f597f2ec2a92fb48a0e4fcfff86191fdebd05354ae1d21fc6d26fc931a471ed3
+  metadata.gz: 109e692e90567fe73e364229dfd1f8553914a85b486f5aa6a80ef6ff43a976533bd84ab730f3cf499bc820a9699c3daf1a48e49e38d188d7c85b3c2279952700
+  data.tar.gz: bc18dd1cc2093a37cd3fa747c25d3ae5ff361f47b4483b5cee991804b3a6f95b2fd2dc4f64311e05cf839cff2cb6afdecfd80e8b691a0132e124debb0b1c10a1

data/README.md

@@ -2,11 +2,11 @@
 
 Seamless and robust Svelte in Rails integration.
 
-By default an when installed together with hotwired/turbo, it renders
+By default, and when installed together with hotwired/turbo, it renders
 svelte components on first request server side («SSR») and for subsequent
-requests it provides a empty tag that is filled up on the frontend by svelte.
+requests it provides a empty tag that will be mounted on the frontend by the associated npm package [@csedl/svelte-on-rails](https://www.npmjs.com/package/@csedl/svelte-on-rails) on the frontend.
 
-This way works perfectly together with turbo, you will never notice 
+This way svelte works perfectly together with turbo. You will never notice 
 this unpleasant «blink» on the frontend and it is maximum performance
 optimized. SSR compilation is handled by rollup.
 
@@ -14,15 +14,19 @@ Server-side rendering is the bottleneck on such a pipeline.
 Although rollup is powerful, this gem is in an early state 
 and there may be limitations.
 
-I have written everything in ESM syntax, orientated by the functionality of vite.
-Although the common-js plugin is installed, I have not tested it, 
+Javascript is written in ESM syntax, orientated by the functionality of vite.
+Although the common-js plugin is installed, I have not tested it,
 so for example `require` may not work in Svelte components.
 
+But we have done everything we can to make your setup work smoothly.
+
 This all is developed on Rails-7 together with `vite_rails`.
 
 Thanks to [shakacode](https://github.com/shakacode/react_on_rails) 
 and [ElMassimo](https://github.com/ElMassimo) because they all helped me with theyr gems.
 
+If you have issues, please open one and contributors are welcome!
+
 ## Requirements
 
 - actual node installed on the server
@@ -58,16 +62,22 @@ On the view
 = svelte_component("myComponent", items: ['item1', 'item2'])
 ```
 
-Within the `components_folder` (configs above) a component like `myComponent.svelte`
+Test: Within the `components_folder` (configs above), create a component like `myComponent.svelte`
 
 ```sveltehtml
 <script>
   export let items
+  let count = 0;
+
+  function increment() {
+    count += 1;
+  }
 </script>
 
 <h1>Greetings from svelte</h1>
 
 <ul>
+  <button on:click={increment}>Increment: {count}</button>
   {#each items as item}
     <li>{item}</li>
   {/each}
@@ -82,6 +92,8 @@ Within the `components_folder` (configs above) a component like `myComponent.sve
 
 And you should see «Greetings from svelte» on the browser.
 
+Click the counter button and check if the component is alive.
+
 I inserted very detailed error messages on rails and on the
 npm package, so please check the logs on your browser.
 
@@ -154,14 +166,16 @@ Example from the rails console for a medium complex component
 - Compiled MyComponent.svelte.js: 0.411ms
   - => happens only once
 - Rendered MyComponent.svelte server-side: 0.518ms
-  - => happens on every request
+  - => happens on every SSR request
+- Rendered MyComponent.svelte as empty element that will be mounted on the client side
+  - => subsequent calls
 - Completed 200 OK in 521ms (Views: 520.2ms | ActiveRecord: 0.0ms (0 queries, 0 cached) | GC: 0.3ms)
 
-Best is to work with the `render_server_side: :auto` option, which you can
-set as default on the config file. Then, the server does the SSR only on 
-initial request and the rest happens on the frontend.
-
 ## Testing
 
 Testings are within the gem by `rspec`. And there is a [rails project](https://gitlab.com/users/sedl/projects) with 
-testings (based on playwright) where the npm package and this gem is tested together.
+testings (based on playwright) where the npm package and this gem is tested together.
+
+## Licence
+
+License is MIT

data/lib/svelte_on_rails/render_server_side.rb

@@ -121,8 +121,11 @@ module SvelteOnRails
     end
 
     def self.file_exist_case_sensitive?(containing_dir, filename)
-      # because some filesystems are case insensitive we test case sensitive
-      Dir[File.join(containing_dir, "*")].select {|f| File.basename(f) == filename}.any?
+      # Combine the directory path and filename
+      full_path = File.join(containing_dir, filename)
+
+      # Check if the file exists and the path matches case-sensitively
+      File.exist?(full_path) && Dir[File.join(containing_dir, "*")].any? { |f| f == full_path }
     end
 
 

data/lib/svelte_on_rails/view_helpers.rb

@@ -68,7 +68,7 @@ module SvelteOnRails
       else
 
         # render empty element
-
+        Rails.logger.info "  Rendered #{filename}.svelte as empty element that will be mounted on the client side"
         content_tag(:div, options) {}
 
       end

data/lib/tasks/svelte_on_rails_tasks.rake

@@ -30,12 +30,16 @@ namespace :svelte_on_rails do
         
         development:
           watch_changes: true
-          # check on every request if any file within the svelte components folder have changed
+          # Check on every request if any file within the svelte components folder have changed, for recompiling
+          # Case sensitive path checking, even the file system is case insensitive
+          # Make sure this ist set to tue for development and test, but not for production
           
         test:
+          watch_changes: true
+          
         production:
       YAML
-      puts "Created configuration file at #{config_path}"
+      puts "Created configuration file at file://#{config_path}"
     end
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: svelte-on-rails
 version: !ruby/object:Gem::Version
-  version: 0.0.10
+  version: 0.0.13
 platform: ruby
 authors:
 - Christian Sedlmair