sygnal 2.1.0 → 2.1.1
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.
- package/README.md +17 -2
- package/package.json +1 -1
- package/sygnal-2.1.0.tgz +0 -0
- package/sygnal-1.2.1.tgz +0 -0
- package/sygnal-2.0.0.tgz +0 -0
- package/sygnal-2.0.1.tgz +0 -0
package/README.md
CHANGED
|
@@ -24,7 +24,7 @@ Sygnal provides a structured way to create Cycle.js components that accomplishes
|
|
|
24
24
|
- Handle all stream plumbing between components
|
|
25
25
|
- Support arbitrarily complex applications with deep component hierarchies
|
|
26
26
|
- Reuse the best patterns from popular frameworks like React and Vue while avoiding the pitfalls
|
|
27
|
-
- Support pure Javascript, Typescript, and JSX
|
|
27
|
+
- Support pure Javascript, Typescript, and JSX (including fragments)
|
|
28
28
|
- Provide application state out of the box, and make it easy to use
|
|
29
29
|
- Use reasonable defaults while providing access to low-level Cycle.js functionality wherever possible
|
|
30
30
|
- Provide automatic debugging information
|
|
@@ -106,7 +106,22 @@ The results will be in the 'dist' folder, and you can serve it locally by runnin
|
|
|
106
106
|
npm preview
|
|
107
107
|
```
|
|
108
108
|
|
|
109
|
-
Alternatively, you can use any other bundler of your choice (Webpack, Babel, Rollup, etc.). To use JSX in your components while using alternative bundlers, you will need to
|
|
109
|
+
Alternatively, you can use any other bundler of your choice (Webpack, Babel, Rollup, etc.). To use JSX in your components while using alternative bundlers, you will need to configure your bundler to use Sygnal's JSX pragma. This is slightly different for each bundler, but looks generally like:
|
|
110
|
+
|
|
111
|
+
```javascript
|
|
112
|
+
// this example is for Vite or esbuild, but most bundlers have options similar to this for handling JSX transpiling
|
|
113
|
+
{
|
|
114
|
+
...,
|
|
115
|
+
esbuild: {
|
|
116
|
+
// add the import for Sygnal's JSX and Fragment handler to the top of each .jsx and .tsx page automatically
|
|
117
|
+
jsxInject: `import { jsx, Fragment } from 'sygnal/jsx'`
|
|
118
|
+
// tell the transpiler to use Sygnal's 'jsx' funtion to render JSX elements
|
|
119
|
+
jsxFactory: `jsx`,
|
|
120
|
+
// tell the transpiler to use Sygnal's 'Fragment' funtion to render JSX fragments (<>...</>)
|
|
121
|
+
jsxFragment: 'Fragment',
|
|
122
|
+
},
|
|
123
|
+
}
|
|
124
|
+
```
|
|
110
125
|
|
|
111
126
|
|
|
112
127
|
## Initialization
|
package/package.json
CHANGED
package/sygnal-2.1.0.tgz
ADDED
|
Binary file
|
package/sygnal-1.2.1.tgz
DELETED
|
Binary file
|
package/sygnal-2.0.0.tgz
DELETED
|
Binary file
|
package/sygnal-2.0.1.tgz
DELETED
|
Binary file
|