node-runner 1.2.0 → 1.3.0
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.
- checksums.yaml +4 -4
- data/CHANGELOG.md +5 -0
- data/README.md +4 -4
- data/lib/version.rb +1 -1
- data/node-runner.gemspec +2 -2
- metadata +5 -5
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: c86125884fd2ac5babe8931308f928f3d0812c0d02a8f1c2d2383058a2e67a97
|
4
|
+
data.tar.gz: 66d565a69bae8e8044dbdc5b3675963280b04eeb3c1b99afbe32628c29410601
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 5e58a2e0bb020bce41b81668faa5d6a47fe9eeaaa73acda41ed6822983bd238eb3728cdcef61d913d526cafa2c263047b4610e3a2e3779d62ff994e6559d5986
|
7
|
+
data.tar.gz: 0c65d16e8e3a200ea929ade970169c14fa051f89418e8131b1dc57df7f7d8789960fca9ae89b294c1b4338ad9f4017f06a42b08c83c7505e845db2571c0ee580
|
data/CHANGELOG.md
CHANGED
data/README.md
CHANGED
@@ -15,7 +15,7 @@ $ bundle add node-runner
|
|
15
15
|
For [Bridgetown](https://www.bridgetownrb.com) websites, you can run an automation to install NodeRunner and set up a builder plugin for further customization.
|
16
16
|
|
17
17
|
```shell
|
18
|
-
bin/bridgetown apply https://
|
18
|
+
bin/bridgetown apply https://codeberg.org/jaredwhite/node-runner/raw/branch/main/bridgetown.automation.rb
|
19
19
|
```
|
20
20
|
|
21
21
|
## Usage
|
@@ -85,9 +85,9 @@ NodeRunner.new "…", executor: NodeRunner::Executor.new(command: "/path/to/cust
|
|
85
85
|
|
86
86
|
A single run of a script is quite fast, nearly as fast as running a script directly with the
|
87
87
|
`node` CLI…because that's essentially what is happening here. However, the performance characteristics using
|
88
|
-
this in a high-traffic request/response cycle
|
88
|
+
this in a high-traffic request/response cycle is unknown. Likely the best context to use
|
89
89
|
Node Runner would be via a background job, or during a build process like when using a static site generator.
|
90
|
-
(Like our parent project [Bridgetown](https://
|
90
|
+
(Like our parent project [Bridgetown](https://www.bridgetownrb.com)!)
|
91
91
|
|
92
92
|
## Testing
|
93
93
|
|
@@ -95,7 +95,7 @@ Node Runner would be via a background job, or during a build process like when u
|
|
95
95
|
|
96
96
|
## Contributing
|
97
97
|
|
98
|
-
1. Fork it (https://
|
98
|
+
1. Fork it (https://codeberg.org/jaredwhite/node-runner/fork)
|
99
99
|
2. Create your feature branch (`git checkout -b my-new-feature`)
|
100
100
|
3. Commit your changes (`git commit -am 'Add some feature'`)
|
101
101
|
4. Push to the branch (`git push origin my-new-feature`)
|
data/lib/version.rb
CHANGED
data/node-runner.gemspec
CHANGED
@@ -8,10 +8,10 @@ Gem::Specification.new do |spec|
|
|
8
8
|
spec.author = "Bridgetown Team"
|
9
9
|
spec.email = "maintainers@bridgetownrb.com"
|
10
10
|
spec.summary = "A simple way to execute Javascript in a Ruby context via Node"
|
11
|
-
spec.homepage = "https://
|
11
|
+
spec.homepage = "https://codeberg.org/jaredwhite/node-runner"
|
12
12
|
spec.license = "MIT"
|
13
13
|
|
14
|
-
spec.required_ruby_version = ">=
|
14
|
+
spec.required_ruby_version = ">= 3.1"
|
15
15
|
|
16
16
|
spec.files = `git ls-files -z`.split("\x0").reject { |f| f.match(%r!^(test|script|spec|features)/!) }
|
17
17
|
spec.require_paths = ["lib"]
|
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: node-runner
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 1.
|
4
|
+
version: 1.3.0
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Bridgetown Team
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date:
|
11
|
+
date: 2025-09-12 00:00:00.000000000 Z
|
12
12
|
dependencies: []
|
13
13
|
description:
|
14
14
|
email: maintainers@bridgetownrb.com
|
@@ -28,7 +28,7 @@ files:
|
|
28
28
|
- lib/node_runner.js
|
29
29
|
- lib/version.rb
|
30
30
|
- node-runner.gemspec
|
31
|
-
homepage: https://
|
31
|
+
homepage: https://codeberg.org/jaredwhite/node-runner
|
32
32
|
licenses:
|
33
33
|
- MIT
|
34
34
|
metadata: {}
|
@@ -40,14 +40,14 @@ required_ruby_version: !ruby/object:Gem::Requirement
|
|
40
40
|
requirements:
|
41
41
|
- - ">="
|
42
42
|
- !ruby/object:Gem::Version
|
43
|
-
version: '
|
43
|
+
version: '3.1'
|
44
44
|
required_rubygems_version: !ruby/object:Gem::Requirement
|
45
45
|
requirements:
|
46
46
|
- - ">="
|
47
47
|
- !ruby/object:Gem::Version
|
48
48
|
version: '0'
|
49
49
|
requirements: []
|
50
|
-
rubygems_version: 3.5.
|
50
|
+
rubygems_version: 3.5.16
|
51
51
|
signing_key:
|
52
52
|
specification_version: 4
|
53
53
|
summary: A simple way to execute Javascript in a Ruby context via Node
|