@pega/custom-dx-components 8.8.6 → 8.8.8

package/README.md

@@ -16,208 +16,6 @@ Ensure you have access to the following in your system:
 
 - System npm version 8
 
-## Initialize a project
+## Latest Documentation
 
-Initialize the project by performing the following procedure in a terminal:
-
-1. Enter the following command to initialize the project.
-
-   Pega 8.7 - `npx @pega/custom-dx-components@1 init`
-
-   Pega 8.8 - `npx @pega/custom-dx-components@2 init`
-
-2. If prompted, enter `y` to install the Custom UI Components package.
-   You will then be asked to set up the project by entering the required details.
-
-3. Enter the following details:
-    - Name of the project (required)
-Example - `mycustomcomponents`
-    - Name of the organization  (required)
-Example - `customorg`
-    - Version  (required)
-Example - `1.0.0`
-    - Description of the project (optional)
-Example - `This project is intended to create and publish a custom component.`
-    - Git repository URL (optional)
-Example - `https://git.custom-components.io/custom-cc.git`
-    - Author (optional)
-   Example - `Michelle`
-
-The workspace is now set up to create custom components and publish them to the server.
-
-## Create custom components
-
-Create custom components using the following procedure:
-
-1. Enter the following command to create a component:
-    `npm run create`
-You will then be asked to enter or review the following details of the component:
-    - Name of the component (required)
-Example - `customcomp0`
-    - Name of component label (required)
-Example - `custom component`
-    - Name of the library (required)
-Example - `basic`
-    - Component version (required)
-Example - `0.0.1`
-    - Type of component (required)
-Example - `Field`
-    - Sub-type of component (required)
-Example - `Text`
-    - Description of the component (optional)
-    Example - `This is a customized searchbox that filters data.`
-The component is created in the following path:  _/Users/your_user_name/project_name/src/components/component_name_
-    You can also pre-configure the values for the above options in a tasks.config.json file as shown below.
-
-        ```json
-        {
-            "component": {
-                "library": "basic",
-                "version": "0.0.1",
-                "type": "field",
-                "subtype": "text",
-                "description": "basic field for capturing textual data",
-                "icon": "basic-field-text.svg"
-            }
-        }
-        ```
->**Note**:
-Alternatively, you can enter the following command to skip entering the details of the component now and can manually enter the details in the config.json file after the component is created:
-`npm run create <enter_component_name>`
-
-A _src/components_ folder is created and the necessary files required to build the component are initialized as seen below.
-
-    ```sh
-    ├── src
-       ├── components
-            ├── <component_name>
-                ├── index.js
-                ├── demo.stories.js
-                ├── config.json
-    ```
-
-
-The *index.js* file contains the actual component rendering logic.
-The *demo.stories.js* file contains the demo that can be viewed in the storybook.
-The *config.json* file contains the mapping of properties for configuring the auto generated property panel. This property panel appears in AppStudio when an application is being authored to use the custom component.
-
-
-2. Enter the following command to start the storybook to view the demo.
-   `npm start`
-
-3. Modify the source files to build your own component. You can also install and import third-party libraries if required for your component.
-
-The custom component is now created. We use the information provided to create uniquely namespaced components in this convention - `<organization>_<library>_<component name>`.
-
-4. local build, you can build the component locally to check for config validation and component validation. Enter
-   `npm buildComponent`
-
-   buildComponent will do the same first 2 steps as publish, but will not publish to the server. This allows you to compile your component locally and fix errors before publish.
-
-## Authenticate the user
-
-Before we publish the custom component to the Pega Infinity Server, authenticate the user to access the resources in the Pega Infinity Server.
-
->**Note**:
-It is required that you configure a value for clientId, clientSecret, and accessTokenUri.
-1. Login to Pega Infinity Server, navigate to Records / Security / OAuth 2.0 Client Registration landing page and open the *DX-CustomComponents* record.
-2. Click **Regenerate Client Secret**, download the Client Credentials (as the Client ID, Client Secret, and Access token endpoint will be needed), and save the record.
-3. Update the the task.config.json file with these downloaded values:
-   ```json
-   "server-config": {
-       "server": "https://127.0.0.1:8080/prweb",
-       "user": "customcomponentoperator",
-       "password": "pwd",
-       "clientId": "<mention client ID here>",
-       "clientSecret": "<mention client secret here>",
-       "accessTokenUri": "https://127.0.0.1:8080/prweb/PRRestService/oauth2/v1/token"
-   },
-   ```
-4. Enter the following command to initiate authentication.
-   `npm run authenticate`
-
-The user is now authenticated and can proceed to either publish or list the components.
-
-## Publish custom components
-Enter the following command to publish custom components to Pega Infinity Server:
-`npm run publish`
-`npm run publishAll`
-Publish the finalized custom components changes to Pega Infinity Server so that it can be discoverable in authoring (design palette).
-You will then be asked to enter the following details:
-
-- The component to be published to Pega Infinity Server. It will be updated if the component exists.
-  - If publishAll, then you won't get a list
-- The name of the ruleset where the component must be published.
-- The version of the ruleset where the component must be published.
-- Specify if the development build should be generated for debugging.
-
-  - If publishAll, will sequentiall go through the list of local components and publish them
-    You can also pre-configure the values for the above options in a tasks.config.json file as shown below. The server, user name, and password must be pre-configured.
-
-        ```json
-        {
-            "components-server-config": {
-                "server": "http://127.0.0.1:8080/prweb",
-                "user": "customcomponentoperator",
-                "password": "pwd"
-                "rulesetName": "TestPega-C11nGall",
-                "rulesetVersion": "01-01-03",
-                "sourceOfComponents": "Server",
-                "devBuild": false,
-            }
-        }
-        ```
-        When the component is successfully published, you can use the newly published component in App Studio's view authoring.
-
-> **Note**:
-> The Rule-UI-Component instance (with component name) is created on the Pega Infinity Server after publishing the component.
-
-## List custom components
-
-View the available components in the local machine or the server.
-
-Enter the following command to list custom components:
-`npm run list`
-
-You will then be asked to enter the following details:
-
-- List components from Server or Local?
-  Example - `Server`
-
-The custom components will now be listed in the terminal.
-
-## Delete custom components
-
-Delete the available or published components in the local machine or the server.
-
-Enter the following command to delete custom components:
-`npm run delete`
-`npm run deleteAll`
-
-You will then be asked to enter the following details:
-
-- Delete components from Server or Local?
-  Example - `Local`
-
-- Select component to delete
-  The list of available components in the following path will be displayed: \_/Users/your_user_name/project_name/src/components
-  Select the component to be deleted from this list.
-- For deleteAll you will see the full list and asked if you want to delete them all.
-
-- Are you sure?
-  Example - `yes`
-
-> **Note**:
-> If you choose to delete components from the server, the successfully published components along with their ruleset name and ruleset version from the Pega Infinity Server will be displayed. Select the component to be deleted from this list.
-
-## View existing custom components in storybook
-
-View custom components in a storybook by performing the following procedure:
-
-1. Enter the following command to open the project.
-   `cd <enter your project's name>`
-
-2. Enter the following command to start the storybook in development mode.
-   `npm start`
-
-The storybook is launched in a browser where you can view the components working in isolation.
+Find the latest documentation on using **DX Component Builder** [here](https://docs.pega.com/bundle/constellation-dx-components-88/page/constellation-dx-components/custom-components/lifecycle-dx-cosmos-components.html)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pega/custom-dx-components",
-  "version": "8.8.6",
+  "version": "8.8.8",
   "description": "Utility for building custom UI components",
   "bin": "./bin/index.js",
   "scripts": {
@@ -18,7 +18,8 @@
     "@babel/preset-env": "^7.19.1",
     "@babel/preset-react": "^7.18.6",
     "adm-zip": "^0.5.9",
-    "ajv": "^8.11.0",
+    "ajv": "^8.12.0",
+    "ajv-keywords": "^5.1.0",
     "arg": "^5.0.2",
     "babel-loader": "^8.2.5",
     "chalk": "^5.0.1",

package/src/tasks/init/index.js

@@ -47,6 +47,7 @@ const copyProjectTemplate = async options => {
     clobber: false
   });
   const packageJsonPath = path.join(options.targetDirectory, 'package.json.mustache');
+  const templateNPMRCPath = path.join(options.targetDirectory, 'templateNPMRC.txt');
 
   let { organization, projectName } = options;
 
@@ -65,6 +66,10 @@ const copyProjectTemplate = async options => {
   const output = compileMustacheTemplate(packageJsonPath, options);
   fs.writeFileSync(packageJsonPath, output);
   fs.renameSync(packageJsonPath, packageJsonPath.replace('.mustache', ''));
+
+  // rename template NPMRC to .npmrc, need to do this because npmjs won't publish an .npmrc file
+  fs.renameSync(templateNPMRCPath, templateNPMRCPath.replace('templateNPMRC.txt', '.npmrc'));
+
   await createLicense(options);
 };
 
@@ -123,7 +128,8 @@ export default async options => {
       },
       {
         title: installDependenciesText,
-        task: () => execPromise('npm i --force --production=false', { cwd: options.targetDirectory })
+        task: () =>
+          execPromise('npm i --force --production=false', { cwd: options.targetDirectory })
       }
     ],
     {

package/src/tasks/init/template/package.json.mustache

@@ -44,7 +44,6 @@
     "@pega/cosmos-react-core": "^3.0.1",
     "@pega/cosmos-react-work": "3.0.1",
     "dayjs": "^1.11.5",
-    "jest": "^29.3.1",
     "polished": "^4.2.2",
     "prop-types": "^15.8.1",
     "react": "^17.0.2",
@@ -57,7 +56,7 @@
   },
   "devDependencies": {
     "@pega/configs": "^0.5.3",
-    "@pega/custom-dx-components": "^8.8.6",
+    "@pega/custom-dx-components": "^8.8.8",
     "@pega/eslint-config": "^0.3.2",
     "@storybook/addon-actions": "^6.5.12",
     "@storybook/addon-essentials": "^6.5.12",

package/src/tasks/init/template/tasks.config.json

@@ -7,7 +7,7 @@
     "devBuild": false,
     "serverType": "infinity",
     "server": "https://localhost:38764/prweb",
-    "clientId": "",
+    "clientId": "10095186356008396159",
     "clientSecret_comment": "Needed only when using 'passwordCreds' or 'clientCreds' grantType",
     "clientSecret": "",
     "grantType": "authCode",
@@ -19,6 +19,7 @@
     "user_and_password_comment": "useful primarily when grantType is set to 'passwordCreds'",
     "user": "",
     "password": "",
+    "questions_comment": "useful for designating certain questions should always or never be asked during npm run authenticate",
     "questions_askAlways": "",
     "questions_askNever": ""
   },

package/src/tasks/init/template/templateNPMRC.txt

@@ -0,0 +1,8 @@
+# Use default npmjs registry for the SDKs
+registry = https://registry.npmjs.org/
+# For now, turn off npm auto-install of peer dependencies to get rid of warnings
+legacy-peer-deps=true
+# Turn off messages such as > react-sdk@0.1.0 list and > dx-component-builder-sdk list
+loglevel=silent
+#
+#

package/src/tasks/publish/helper.js

@@ -137,7 +137,14 @@ export const publishComponentToServer = async data => {
             throw new Error(`${respData.message}`);
           }
         })
-        .catch(e => Promise.reject(`${chalk.bold.red(e)}`));
+        .catch( e => {
+          if (e.code == 'ECONNREFUSED') {
+            Promise.reject(`${chalk.bold.red('Error occurred in authentication. Please regenerate using authenticate')}`);
+          }
+          else {
+            Promise.reject(`${chalk.bold.red(e)}`);
+          }
+        })
     } else {
       throw new Error(`Error occurred in authentication. Please regenerate using authenticate`);
     }

package/src/util.js

@@ -282,6 +282,17 @@ export const showVersion = () => {
   const pData = require("@pega/custom-dx-components/package.json");
 
   console.log(chalk.green("DX Component Builder v" + pData.version));
+
+  // do a check of node version, it should be 18 or greater
+  const arNodeVersion  = process.versions.node.split(".");
+
+  const nodeMajorVersion = parseInt(arNodeVersion[0]);
+  const nodeMinorVersion = parseInt(arNodeVersion[1]);
+
+  if (nodeMajorVersion < 18) {
+    console.log(chalk.redBright("DX Component Builder - SDK requires node v18 or greater, current version: " + process.version));
+    process.exit(1);
+  }
 };
 
 export const getOOTBComponents = async () => {