@intuned/runtime-dev 1.0.6-cli.8.3.1 → 1.0.6-cli.8.3.2

package/bin/cli-build

@@ -0,0 +1,3 @@
+#!/usr/bin/env node
+
+require("../dist/commands/cli-build/cli-build.js");

package/bin/run-api

@@ -0,0 +1,3 @@
+#!/usr/bin/env node
+
+require("../dist/commands/run-api-cli/run-api.js");

package/dist/commands/{intuned-build-project/intuned-build-project.js → cli-build/cli-build.js}

@@ -8,7 +8,7 @@ function _interopRequireDefault(e) { return e && e.__esModule ? e : { default: e
 _dotenv.default.config({
   path: `.env`
 });
-_commander.program.name("intuned-build-project").description("Build your current Inuned project").action(async () => {
+_commander.program.name("intuned-build-project").description("Build your current Intuned project").action(async () => {
   try {
     await (0, _utils.runBuild)();
   } catch (error) {

package/dist/commands/deploy/deploy.js

@@ -37,7 +37,7 @@ _commander.program.description("Deploy an Intuned project to be public").argumen
     if (!deployDone) {
       throw new Error(`Project not deployed: ${deployErrorMessage}`);
     }
-    const url = process.env.DOMAIN || `https://app.intuned.io`;
+    const url = process.env.INTUNED_API_DEV_DOMAIN || `https://app.intuned.io`;
     console.log(_chalk.default.green(`\n✅ Project "${_projectName}" deployed successfully!` + `\n\nYou can check your project on the platform: ${_chalk.default.bold(`${url}/projects/${projectId}/details`)}\n`));
   } catch (error) {
     console.error(_chalk.default.red(`\n${error.message}`));

package/dist/commands/deploy/utils.js

@@ -117,7 +117,7 @@ async function deployProject(projectName, auth) {
     workspaceId,
     apiKey
   } = auth;
-  const baseUrl = process.env.DOMAIN || `https://app.intuned.io`;
+  const baseUrl = process.env.INTUNED_API_DEV_DOMAIN || `https://app.intuned.io`;
   const url = `${baseUrl}/api/v1/workspace/${workspaceId}/projects/create`;
   const headers = {
     "x-api-key": apiKey,
@@ -125,6 +125,11 @@ async function deployProject(projectName, auth) {
   };
   const projectPath = process.cwd();
   const codeTree = await convertProjectToCodeTree(projectPath);
+  codeTree["tsconfig.json"] = {
+    file: {
+      contents: JSON.stringify(_constants.tsConfigCli, null, 2)
+    }
+  };
   const deployProjectPayload = {
     name: projectName,
     codeTree,
@@ -287,7 +292,7 @@ const validateIntunedProject = async () => {
 exports.validateIntunedProject = validateIntunedProject;
 const checkIntunedProjectDeployStatus = async (workspaceId, projectName, apiKey) => {
   try {
-    const baseUrl = process.env.DOMAIN || `https://app.intuned.io`;
+    const baseUrl = process.env.INTUNED_API_DEV_DOMAIN || `https://app.intuned.io`;
     const url = `${baseUrl}/api/v1/workspace/${workspaceId}/projects/create/${projectName}/result`;
     const headers = {
       "x-api-key": apiKey,
@@ -329,7 +334,7 @@ const runBuild = async () => {
   if (await fs.exists(distPath)) {
     await fs.remove(distPath);
   }
-  const buildCommand = "npx tsc";
+  const buildCommand = "tsc";
   try {
     await execPromise(buildCommand, {
       cwd: currentProjectDirectory

package/dist/commands/init/utils.js

@@ -77,7 +77,7 @@ function getAuthCredentials(options) {
     });
   }
   if (missingAuth.length) {
-    throw new Error("Authentication details are required. Please provide them via command line options or environment variables.");
+    throw new Error(`Authentication failed: Missing ${missingAuth.join(" and ")}.\n\n` + `To fix this issue:\n\n` + `1. For workspaceId:\n` + `   - Add it to your intuned.json file under the "workspaceId" property\n` + `   - OR provide via command line: --workspace-id YOUR_WORKSPACE_ID\n` + `   - See how to get your workspaceId: https://docs.intunedhq.com/docs/guides/platform/how-to-get-a-workspace-id\n\n` + `2. For API key:\n` + `   - Include in your .env file INTUNED_API_KEY=your_api_key_here \n` + `   - OR provide via command line: --api-key YOUR_API_KEY\n\n` + `Run commands from the project root directory where intuned.json is located.`);
   }
   return {
     workspaceId,
@@ -144,7 +144,7 @@ async function scaffoldProject(templateId, isTargetDirectoryEmpty) {
   }));
 }
 async function fetchProjectTemplate(templateId) {
-  const baseUrl = process.env.DOMAIN || `https://app.intuned.io`;
+  const baseUrl = process.env.INTUNED_API_DEV_DOMAIN || `https://app.intuned.io`;
   const url = `${baseUrl}/api/templates/${templateId}`;
   const response = await fetch(url);
   if (!response.ok) {

package/dist/common/cli/cliReadme.d.ts

@@ -1 +1 @@
-export declare const cliReadme = "# Intuned CLI\n\n## Usage Instructions\n\nThe Intuned CLI exposes a variaty of commands to develop and create your Intuned projects locally:\n\n### Init a project\n\n`npx -p @intuned/runtime intuned-init`\n\n### Artifacts provided\n\n- `./intuned.json`: Intuned project configuration file\n- `./api`: Folder containing the API files\n- `./parameters`: Folder containing the parameters files, used for API parameters injection\n- `./output`: Folder containing the output files generated by the APIs\n\n### Note:\n\n- You can use either `yarn` or `npm run` to run and execute the commands\n\n### Keys,Environment Variables and Settings\n\n- workspaceId: Your Intuned workspace ID, either provided via command line or Intuned.json setting -> (`workspaceId`)\n- projectName: The name of your Intuned project, either provided via command line or Intuned.json setting -> (`projectName`)\n- INTUNED_API_KEY: Your Intuned API key, either provided via command line or environment variable\n\n### Running the APIs through development\n\n`yarn run-api` <api-name>\n\n- Options:\n  - -i, --parameters-file <file>: JSON file containing API parameters\n  - -s, --store-results: Store the results of the running API inside the output directory:\n    - ./output/[runId]/results.json\n    - ./output/[runId]/extendedPayloads.json\n\n### Building the intuned project\n\n`yarn cli-build`\n\n### Deploying the project\n\n`yarn deploy` <project-name>\n\n- <project-name>: Optional project name that overrides the one on the intuned.json file\n- Options (optinal):\n  - --workspace-id: Overrides the workspace id specified in the intuned.json file setting\n  - --api-key: Overrides the api key provided by the environment var.\n\n### General Notes:\n\n- You can interact with your Intuned project within the platform when deploying it\n- All commands above should be runned from the root location of the project (from where you runned and created the project through `intuned-init` command)\n- Verify you're in the correct location by confirming the presence of package.json and intuned.json files\n- Running commands from subdirectories may result in errors or unexpected behavior";
+export declare const cliReadme = "# Intuned CLI\n## Introduction\nThe Intuned CLI exposes a variaty of commands to develop your Intuned projects locally\n\n## Development Commands\n\n### Initialize a Project\n`npx -p @intuned/runtime init`\n\n### Run an API\n`yarn run-api <api-name>`\n\nOptions:\n- `-i, --parameters-file file-path`: JSON file containing API parameters\n- `-s, --store-results`: Store the results in `./output/[runId]/results.json` and `./output/[runId]/extendedPayloads.json`\n\n### Build a Project\n`yarn cli-build`\n\n### Deploy a Project\n`yarn deploy <project-name>`\n\n- `project-name`: Optional name that overrides the one in intuned.json\n- Options:\n  - `--workspace-id`: Overrides the workspace ID in intuned.json\n  - `--api-key`: Overrides the API key from environment variables\n\n## Configuration\n\n### Environment Variables and Settings\n- `workspaceId`: Your Intuned workspace ID ([How to get your workspaceId](https://docs.intunedhq.com/docs/guides/platform/how-to-get-a-workspace-id))\n  - Set in `intuned.json` file under the `workspaceId` property\n  - Or provide via CLI with `--workspace-id` flag during deployment\n  \n- `projectName`: The name of your Intuned project\n  - Set in `intuned.json` file under the `projectName` property\n  - Or override via command line when deploying with `yarn deploy my-project-name`\n  \n- `INTUNED_API_KEY`: Your Intuned API key\n  - Set as an environment variable: `export INTUNED_API_KEY=your_api_key_here`\n  - Or include in your .env file for development\n  - Or provide via CLI with `--api-key` flag during deployment\n\n## Project Structure\n\n### Generated Artifacts\n- `./intuned.json`: Project configuration file\n- `./api`: Folder containing API implementation files\n- `./parameters`: Folder for API parameters injection\n- `./output`: Folder containing generated output files\n\n### Notes\n- You can use either `yarn` or `npm run` to execute commands\n- All commands must be run from the project root directory\n- Verify you're in the correct location by confirming the presence of package.json and intuned.json\n- Running commands from subdirectories may result in errors\n- You can manage your deployed projects through the Intuned platform\n- WARNING: \u26A0\uFE0F Changes to TS Config may break some Intuned functionalities\n";

package/dist/common/cli/cliReadme.js

@@ -5,58 +5,61 @@ Object.defineProperty(exports, "__esModule", {
 });
 exports.cliReadme = void 0;
 const cliReadme = exports.cliReadme = `# Intuned CLI
+## Introduction
+The Intuned CLI exposes a variaty of commands to develop your Intuned projects locally
 
-## Usage Instructions
+## Development Commands
 
-The Intuned CLI exposes a variaty of commands to develop and create your Intuned projects locally:
+### Initialize a Project
+\`npx -p @intuned/runtime init\`
 
-### Init a project
+### Run an API
+\`yarn run-api <api-name>\`
 
-\`npx -p @intuned/runtime intuned-init\`
-
-### Artifacts provided
-
-- \`./intuned.json\`: Intuned project configuration file
-- \`./api\`: Folder containing the API files
-- \`./parameters\`: Folder containing the parameters files, used for API parameters injection
-- \`./output\`: Folder containing the output files generated by the APIs
-
-### Note:
-
-- You can use either \`yarn\` or \`npm run\` to run and execute the commands
-
-### Keys,Environment Variables and Settings
-
-- workspaceId: Your Intuned workspace ID, either provided via command line or Intuned.json setting -> (\`workspaceId\`)
-- projectName: The name of your Intuned project, either provided via command line or Intuned.json setting -> (\`projectName\`)
-- INTUNED_API_KEY: Your Intuned API key, either provided via command line or environment variable
-
-### Running the APIs through development
-
-\`yarn run-api\` <api-name>
-
-- Options:
-  - -i, --parameters-file <file>: JSON file containing API parameters
-  - -s, --store-results: Store the results of the running API inside the output directory:
-    - ./output/[runId]/results.json
-    - ./output/[runId]/extendedPayloads.json
-
-### Building the intuned project
+Options:
+- \`-i, --parameters-file file-path\`: JSON file containing API parameters
+- \`-s, --store-results\`: Store the results in \`./output/[runId]/results.json\` and \`./output/[runId]/extendedPayloads.json\`
 
+### Build a Project
 \`yarn cli-build\`
 
-### Deploying the project
-
-\`yarn deploy\` <project-name>
+### Deploy a Project
+\`yarn deploy <project-name>\`
 
-- <project-name>: Optional project name that overrides the one on the intuned.json file
-- Options (optinal):
-  - --workspace-id: Overrides the workspace id specified in the intuned.json file setting
-  - --api-key: Overrides the api key provided by the environment var.
-
-### General Notes:
-
-- You can interact with your Intuned project within the platform when deploying it
-- All commands above should be runned from the root location of the project (from where you runned and created the project through \`intuned-init\` command)
-- Verify you're in the correct location by confirming the presence of package.json and intuned.json files
-- Running commands from subdirectories may result in errors or unexpected behavior`;
+- \`project-name\`: Optional name that overrides the one in intuned.json
+- Options:
+  - \`--workspace-id\`: Overrides the workspace ID in intuned.json
+  - \`--api-key\`: Overrides the API key from environment variables
+
+## Configuration
+
+### Environment Variables and Settings
+- \`workspaceId\`: Your Intuned workspace ID ([How to get your workspaceId](https://docs.intunedhq.com/docs/guides/platform/how-to-get-a-workspace-id))
+  - Set in \`intuned.json\` file under the \`workspaceId\` property
+  - Or provide via CLI with \`--workspace-id\` flag during deployment
+  
+- \`projectName\`: The name of your Intuned project
+  - Set in \`intuned.json\` file under the \`projectName\` property
+  - Or override via command line when deploying with \`yarn deploy my-project-name\`
+  
+- \`INTUNED_API_KEY\`: Your Intuned API key
+  - Set as an environment variable: \`export INTUNED_API_KEY=your_api_key_here\`
+  - Or include in your .env file for development
+  - Or provide via CLI with \`--api-key\` flag during deployment
+
+## Project Structure
+
+### Generated Artifacts
+- \`./intuned.json\`: Project configuration file
+- \`./api\`: Folder containing API implementation files
+- \`./parameters\`: Folder for API parameters injection
+- \`./output\`: Folder containing generated output files
+
+### Notes
+- You can use either \`yarn\` or \`npm run\` to execute commands
+- All commands must be run from the project root directory
+- Verify you're in the correct location by confirming the presence of package.json and intuned.json
+- Running commands from subdirectories may result in errors
+- You can manage your deployed projects through the Intuned platform
+- WARNING: ⚠️ Changes to TS Config may break some Intuned functionalities
+`;

package/dist/common/cli/types.js

@@ -4,4 +4,4 @@ Object.defineProperty(exports, "__esModule", {
   value: true
 });
 exports.templateIds = void 0;
-const templateIds = exports.templateIds = ["default", "empty", "linkedin-recorder", "api-auth-sessions", "nested-scheduling", "ai-extractors", "npm-auth-sessions", "python-empty"];
+const templateIds = exports.templateIds = ["default", "empty", "linkedin-recorder", "api-auth-sessions", "nested-scheduling", "ai-extractors", "npm-auth-sessions"];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@intuned/runtime-dev",
-  "version": "1.0.6-cli.8.3.1",
+  "version": "1.0.6-cli.8.3.2",
   "description": "Intuned runtime",
   "exports": {
     ".": "./dist/index.js",
@@ -50,10 +50,10 @@
     "intuned-browser-start": "./bin/intuned-browser-start",
     "intuned-browser-save-state": "./bin/intuned-browser-save-state",
     "intuned-ts-check": "./bin/intuned-ts-check",
-    "intuned-init": "./bin/intuned-init",
-    "intuned-run": "./bin/intuned-run",
-    "intuned-deploy": "./bin/intuned-deploy",
-    "intuned-build-project": "./bin/intuned-build-project"
+    "init": "./bin/intuned-init",
+    "run-api": "./bin/intuned-run",
+    "deploy": "./bin/intuned-deploy",
+    "cli-build": "./bin/intuned-build-project"
   },
   "dependencies": {
     "@babel/plugin-syntax-dynamic-import": "^7.8.3",
@@ -70,7 +70,7 @@
     "applicationinsights": "^2.9.2",
     "async-retry": "^1.3.3",
     "babel-plugin-dynamic-import-node": "^2.3.3",
-    "boxen": "^8.0.1",
+    "boxen": "8.0.1",
     "chalk": "^4.1.2",
     "commander": "^11.0.0",
     "cross-fetch": "^4.0.0",
@@ -81,11 +81,11 @@
     "fs-extra": "^11.3.0",
     "https-proxy-agent": "^7.0.5",
     "image-size": "^1.1.1",
-    "inquirer": "^12.6.0",
+    "inquirer": "12.6.0",
     "jsonwebtoken": "^9.0.2",
     "lodash": "^4.17.21",
     "milliparsec": "^2.3.0",
-    "minimatch": "^10.0.1",
+    "minimatch": "10.0.1",
     "ms": "^2.1.3",
     "nanoid": "3",
     "neverthrow": "^6.1.0",

package/bin/intuned-build-project

@@ -1,3 +0,0 @@
-#!/usr/bin/env node
-
-require("../dist/commands/intuned-build-project/intuned-build-project.js");

package/bin/intuned-run

@@ -1,3 +0,0 @@
-#!/usr/bin/env node
-
-require("../dist/commands/intuned-run/intuned-run.js");