@open-pioneer/vite-plugin-pioneer 2.0.1 → 3.0.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/CHANGELOG.md CHANGED
@@ -1,5 +1,28 @@
1
1
  # Changelog @open-pioneer/vite-plugin-pioneer
2
2
 
3
+ ## 3.0.1
4
+
5
+ ### Patch Changes
6
+
7
+ - 017b8f3: Harmonize naming of Open Pioneer Trails in READMEs, package.json files and error messages.
8
+ - Updated dependencies [017b8f3]
9
+ - @open-pioneer/build-common@2.0.3
10
+
11
+ ## 3.0.0
12
+
13
+ ### Major Changes
14
+
15
+ - c08520d: Switch to `type`: `module`
16
+ - c08520d: Add support for vite 5.
17
+
18
+ ### Patch Changes
19
+
20
+ - c08520d: Update zod-validation-error to 3.x
21
+ - c08520d: Update dependencies
22
+ - Updated dependencies [c08520d]
23
+ - Updated dependencies [c08520d]
24
+ - @open-pioneer/build-common@2.0.2
25
+
3
26
  ## 2.0.1
4
27
 
5
28
  ### Patch Changes
@@ -49,14 +72,14 @@
49
72
 
50
73
  ### Patch Changes
51
74
 
52
- - 99354bf: Improve error message when two versions of the same pioneer package are encountered.
53
- Only a single version per pioneer package per app is supported: all packages must share the same version and location on disk.
75
+ - 99354bf: Improve error message when two versions of the same Trails package are encountered.
76
+ Only a single version per Trails package per app is supported: all packages must share the same version and location on disk.
54
77
 
55
78
  The vite overlay in the browser now shows a comprehensible error message such as this:
56
79
 
57
80
  ```text
58
81
  [plugin:pioneer:codegen] Encountered the package '@open-pioneer/runtime' at two different locations.
59
- Pioneer packages cannot be used more than once in the same application.
82
+ Trails packages cannot be used more than once in the same application.
60
83
  All packages must use a common version of '@open-pioneer/runtime'.
61
84
 
62
85
  1. @open-pioneer/runtime@1.0.0 at $HOME/projects/pioneer/starter/node_modules/.pnpm/@open-pioneer+runtime@1.0.0_@formatjs+intl@2.9.0_@open-pioneer+chakra-integration@1.0.0_@open_4cza3noe47gq2v2rsqn2cypo4q/node_modules/@open-pioneer/runtime
@@ -108,7 +131,7 @@
108
131
  - cf32df5: Add another workaround that unfortunately currently requires pnpm's `shamefully-hoist` option.
109
132
 
110
133
  [`shamefully-hoist`](https://pnpm.io/npmrc#shamefully-hoist) allows the application to 'see' all other installed node packages.
111
- This is usually a bad practice but we currently require it for the virtual module that imports all open pioneer services.
134
+ This is usually a bad practice but we currently require it for the virtual module that imports all Open Pioneer Trails services.
112
135
  For more details see the linked commit.
113
136
 
114
137
  ## 0.8.5
package/README.md CHANGED
@@ -1,6 +1,8 @@
1
1
  # @open-pioneer/vite-plugin-pioneer
2
2
 
3
- The vite plugin provided by this package is required by open pioneer trails applications.
3
+ The vite plugin provided by this package is required by Open Pioneer Trails applications.
4
+
5
+ This plugin supports vite `4.x` and `5.x`.
4
6
 
5
7
  Usage:
6
8
 
@@ -98,7 +100,7 @@ export interface AdvancedAppOptions {
98
100
  ### Multi page support
99
101
 
100
102
  Vite is by default configured to create a single page application (i.e. a single html file with assets).
101
- The pioneer repository supports multiple deployment modes that can each be achieved by configuring this plugin:
103
+ The Open Pioneer Trails repository supports multiple deployment modes that can each be achieved by configuring this plugin:
102
104
 
103
105
  1. Building a single page application.
104
106
  Configure `rootSite: true` and leave `sites` and `apps` empty.
package/client.d.ts CHANGED
@@ -9,7 +9,7 @@ declare module "open-pioneer:app" {
9
9
 
10
10
  /**
11
11
  * Provides react hooks to a module.
12
- * The module must be inside a valid pioneer package (or app).
12
+ * The module must be inside a valid Open Pioneer Trails package (or app).
13
13
  *
14
14
  * The generated hooks will ensure that hooks return data structures and services
15
15
  * for the correct package, and that dependency declarations are valid.