piral-lazy 0.15.3-beta.4955 → 0.15.3-beta.4975

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 (2) hide show
  1. package/README.md +3 -3
  2. package/package.json +3 -3
package/README.md CHANGED
@@ -12,14 +12,14 @@ By default, these API extensions are not integrated in `piral`, so you'd need to
12
12
 
13
13
  Lazy loading of data or other dependencies can be crucial in more complex scenarios. It should not be necessary to include everything in one load to bring a pilet or components of it to live.
14
14
 
15
- `piral-lazy` allows defining generic dependencies that will be loaded *before* loading / using a component. The provided helpers which are exposed via the pilet API give you the power to
15
+ `piral-lazy` allows defining generic dependencies that will be loaded *before* loading/using a component. The provided helpers which are exposed via the pilet API give you the power to
16
16
 
17
17
  1. define new dependencies (given by a unique name and a loader function) and
18
- 2. rely on defined dependencies before actually loading / trying to render a component.
18
+ 2. rely on defined dependencies before actually loading/trying to render a component.
19
19
 
20
20
  If your pilets use lazy loading in some way then `piral-lazy` may be the right choice. Also, if your pilets are too large and could benefit from further resource sharing and lazy loading then this plugin could be helpful. `piral-lazy` remains framework agnostic and thus works beyond React.
21
21
 
22
- Alternative: Just define / use what is there out of the box. By using `React.lazy` together with bundle splitting most of the things may be already properly transported. Remember that you could also lazy load context that provide your dependencies - thus making `React.lazy` a single solution (if your framework is "React").
22
+ Alternative: Just define/use what is there out of the box. By using `React.lazy` together with bundle splitting most of the things may be already properly transported. Remember that you could also lazy load context that provide your dependencies - thus making `React.lazy` a single solution (if your framework is "React").
23
23
 
24
24
  ## Documentation
25
25
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "piral-lazy",
3
- "version": "0.15.3-beta.4955",
3
+ "version": "0.15.3-beta.4975",
4
4
  "description": "Plugin for lazy loading third-party framework components in Piral.",
5
5
  "keywords": [
6
6
  "piral",
@@ -61,12 +61,12 @@
61
61
  },
62
62
  "devDependencies": {
63
63
  "@types/react": "^18.0.0",
64
- "piral-core": "0.15.3-beta.4955",
64
+ "piral-core": "0.15.3-beta.4975",
65
65
  "react": "^18.0.0"
66
66
  },
67
67
  "peerDependencies": {
68
68
  "piral-core": "0.14.x || 0.15.x",
69
69
  "react": ">=16.8.0"
70
70
  },
71
- "gitHead": "598563720dff2995e2ccc4acb07167554ce788d9"
71
+ "gitHead": "5cf09cee48aa723ebe3fa9e48a98ff118f3cb6dc"
72
72
  }