piral-cli 0.14.0-pre.3097 → 0.14.0-pre.3113
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/lib/messages.d.ts +1 -1
- package/lib/messages.js +1 -1
- package/package.json +2 -2
- package/src/messages.ts +14 -14
package/lib/messages.d.ts
CHANGED
|
@@ -142,7 +142,7 @@ export declare function appInstanceNotFound_0010(name: string): QuickMessage;
|
|
|
142
142
|
* It should be an HTML file.
|
|
143
143
|
*
|
|
144
144
|
* @see
|
|
145
|
-
* - [Parcel HTML Asset](https://parceljs.org/html
|
|
145
|
+
* - [Parcel HTML Asset](https://parceljs.org/languages/html/)
|
|
146
146
|
*
|
|
147
147
|
* @example
|
|
148
148
|
* Make sure the package.json of the Piral instance is valid (has an "app" field).
|
package/lib/messages.js
CHANGED
|
@@ -164,7 +164,7 @@ exports.appInstanceNotFound_0010 = appInstanceNotFound_0010;
|
|
|
164
164
|
* It should be an HTML file.
|
|
165
165
|
*
|
|
166
166
|
* @see
|
|
167
|
-
* - [Parcel HTML Asset](https://parceljs.org/html
|
|
167
|
+
* - [Parcel HTML Asset](https://parceljs.org/languages/html/)
|
|
168
168
|
*
|
|
169
169
|
* @example
|
|
170
170
|
* Make sure the package.json of the Piral instance is valid (has an "app" field).
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "piral-cli",
|
|
3
|
-
"version": "0.14.0-pre.
|
|
3
|
+
"version": "0.14.0-pre.3113",
|
|
4
4
|
"description": "The standard CLI for creating and building a Piral instance or a Pilet.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"portal",
|
|
@@ -77,5 +77,5 @@
|
|
|
77
77
|
"typescript": "^4.0.2",
|
|
78
78
|
"yargs": "^15.4.1"
|
|
79
79
|
},
|
|
80
|
-
"gitHead": "
|
|
80
|
+
"gitHead": "1cb567aea336aa9ffde6d8a33f5a1d4fc36e681f"
|
|
81
81
|
}
|
package/src/messages.ts
CHANGED
|
@@ -161,7 +161,7 @@ export function appInstanceNotFound_0010(name: string): QuickMessage {
|
|
|
161
161
|
* It should be an HTML file.
|
|
162
162
|
*
|
|
163
163
|
* @see
|
|
164
|
-
* - [Parcel HTML Asset](https://parceljs.org/html
|
|
164
|
+
* - [Parcel HTML Asset](https://parceljs.org/languages/html/)
|
|
165
165
|
*
|
|
166
166
|
* @example
|
|
167
167
|
* Make sure the package.json of the Piral instance is valid (has an "app" field).
|
|
@@ -1277,10 +1277,10 @@ export function failedHttpGet_0068(error: string): QuickMessage {
|
|
|
1277
1277
|
*
|
|
1278
1278
|
* @abstract
|
|
1279
1279
|
* While submitting the HTTP get request an error was reported.
|
|
1280
|
-
*
|
|
1280
|
+
*
|
|
1281
1281
|
* Potentially, the server returned some more indicative error message. In this
|
|
1282
1282
|
* case read it carefully to know what version was already published.
|
|
1283
|
-
*
|
|
1283
|
+
*
|
|
1284
1284
|
* In any case only the documentation of the corresponding feed service can be
|
|
1285
1285
|
* conclusive how this can be resolved. Presumably, some payment of some fee
|
|
1286
1286
|
* is necessary to publish pilets.
|
|
@@ -1299,28 +1299,28 @@ export function failedToUploadPayment_0161(response: any): QuickMessage {
|
|
|
1299
1299
|
*
|
|
1300
1300
|
* @abstract
|
|
1301
1301
|
* While submitting the HTTP get request an error was reported.
|
|
1302
|
-
*
|
|
1302
|
+
*
|
|
1303
1303
|
* Potentially, the server returned some more indicative error message. In this
|
|
1304
1304
|
* case read it carefully to know what version was already published.
|
|
1305
|
-
*
|
|
1305
|
+
*
|
|
1306
1306
|
* In any case you need to change the version to continue. You can do that by
|
|
1307
1307
|
* editing the "version" field in the pilet's package.json or using `npm version`.
|
|
1308
1308
|
*
|
|
1309
1309
|
* @example
|
|
1310
1310
|
* If you already published the pilet, e.g., via
|
|
1311
|
-
*
|
|
1311
|
+
*
|
|
1312
1312
|
* ```sh
|
|
1313
1313
|
* pilet publish --api-key ... --url ...
|
|
1314
1314
|
* ```
|
|
1315
|
-
*
|
|
1315
|
+
*
|
|
1316
1316
|
* then doing this again without any change should result in this error.
|
|
1317
|
-
*
|
|
1317
|
+
*
|
|
1318
1318
|
* Now we can patch-upgrade the version of the pilet:
|
|
1319
|
-
*
|
|
1319
|
+
*
|
|
1320
1320
|
* ```sh
|
|
1321
1321
|
* npm version patch
|
|
1322
1322
|
* ```
|
|
1323
|
-
*
|
|
1323
|
+
*
|
|
1324
1324
|
* And try the `pilet publish` command again. This time it should just work.
|
|
1325
1325
|
*/
|
|
1326
1326
|
export function failedToUploadVersion_0162(response: any): QuickMessage {
|
|
@@ -1337,10 +1337,10 @@ export function failedToUploadVersion_0162(response: any): QuickMessage {
|
|
|
1337
1337
|
*
|
|
1338
1338
|
* @abstract
|
|
1339
1339
|
* While submitting the HTTP get request an error was reported.
|
|
1340
|
-
*
|
|
1340
|
+
*
|
|
1341
1341
|
* Potentially, the server returned some more indicative error message. In this
|
|
1342
1342
|
* case read it carefully to know how much the limit was exceeded.
|
|
1343
|
-
*
|
|
1343
|
+
*
|
|
1344
1344
|
* In any case the pilet must be somehow trimmed down. Most often, the size is
|
|
1345
1345
|
* dominantly determined by some external packages that are referened. Use a
|
|
1346
1346
|
* page such as bundlephobia.com or some IDE tools to find out which packages
|
|
@@ -1960,7 +1960,7 @@ export function publishProviderMissing_0113(providerName: string, availableProvi
|
|
|
1960
1960
|
* ```sh
|
|
1961
1961
|
* piral publish --type release --provider xcopy --fields.target "/temp/dest"
|
|
1962
1962
|
* ```
|
|
1963
|
-
*
|
|
1963
|
+
*
|
|
1964
1964
|
* The type is "release".
|
|
1965
1965
|
*/
|
|
1966
1966
|
export function publishEmulatorSourcesInvalid_0114(): QuickMessage {
|
|
@@ -2018,7 +2018,7 @@ export function failedToOpenBrowser_0170(error: string): QuickMessage {
|
|
|
2018
2018
|
*
|
|
2019
2019
|
* The v1 version has better support for older browsers, but requires a polyfill to work
|
|
2020
2020
|
* correctly. This polyfill is part of the standard Piral polyfills.
|
|
2021
|
-
*
|
|
2021
|
+
*
|
|
2022
2022
|
* The v2 version uses a SystemJS format for the pilet. It has the broadest browser support
|
|
2023
2023
|
* but requires the custom format as output. Most bundlers support SystemJS directly or
|
|
2024
2024
|
* indirectly, making it a quite broad choice.
|