projen 0.99.34 → 0.99.36

package/lib/javascript/node-package.d.ts

@@ -21,11 +21,11 @@ export interface NodePackageOptions {
      * Runtime dependencies of this module.
      *
      * The recommendation is to only specify the module name here (e.g.
-     * `express`). This will behave similar to `yarn add` or `npm install` in the
+     * `express`). This will behave similar to `pnpm add` or `npm install` in the
      * sense that it will add the module as a dependency to your `package.json`
      * file with the latest version (`^`). You can specify semver requirements in
-     * the same syntax passed to `npm i` or `yarn add` (e.g. `express@^2`) and
-     * this will be what you `package.json` will eventually include.
+     * the same syntax passed to `pnpm add` or `npm i` (e.g. `express@^2`) and
+     * this will be what your `package.json` will eventually include.
      *
      * @example [ 'express', 'lodash', 'foo@^2' ]
      * @default []
@@ -38,11 +38,11 @@ export interface NodePackageOptions {
      * module is consumed.
      *
      * The recommendation is to only specify the module name here (e.g.
-     * `express`). This will behave similar to `yarn add` or `npm install` in the
+     * `express`). This will behave similar to `pnpm add` or `npm install` in the
      * sense that it will add the module as a dependency to your `package.json`
      * file with the latest version (`^`). You can specify semver requirements in
-     * the same syntax passed to `npm i` or `yarn add` (e.g. `express@^2`) and
-     * this will be what you `package.json` will eventually include.
+     * the same syntax passed to `pnpm add` or `npm i` (e.g. `express@^2`) and
+     * this will be what your `package.json` will eventually include.
      *
      * @example [ 'typescript', '@types/express' ]
      * @default []
@@ -73,11 +73,11 @@ export interface NodePackageOptions {
      * your `package.json`.
      *
      * The recommendation is to only specify the module name here (e.g.
-     * `express`). This will behave similar to `yarn add` or `npm install` in the
+     * `express`). This will behave similar to `pnpm add` or `npm install` in the
      * sense that it will add the module as a dependency to your `package.json`
      * file with the latest version (`^`). You can specify semver requirements in
-     * the same syntax passed to `npm i` or `yarn add` (e.g. `express@^2`) and
-     * this will be what you `package.json` will eventually include.
+     * the same syntax passed to `pnpm add` or `npm i` (e.g. `express@^2`) and
+     * this will be what your `package.json` will eventually include.
      */
     readonly bundledDeps?: string[];
     /**
@@ -569,9 +569,9 @@ export declare class NodePackage extends Component {
      * Defines normal dependencies.
      *
      * @param deps Names modules to install. By default, the the dependency will
-     * be installed in the next `npx projen` run and the version will be recorded
-     * in your `package.json` file. You can upgrade manually or using `yarn
-     * add/upgrade`. If you wish to specify a version range use this syntax:
+     * be installed in the next `pnpm projen` run and the version will be recorded
+     * in your `package.json` file. You can upgrade manually or using `pnpm
+     * add/update`. If you wish to specify a version range use this syntax:
      * `module@^7`.
      */
     addDeps(...deps: string[]): void;
@@ -579,9 +579,9 @@ export declare class NodePackage extends Component {
      * Defines development/test dependencies.
      *
      * @param deps Names modules to install. By default, the the dependency will
-     * be installed in the next `npx projen` run and the version will be recorded
-     * in your `package.json` file. You can upgrade manually or using `yarn
-     * add/upgrade`. If you wish to specify a version range use this syntax:
+     * be installed in the next `pnpm projen` run and the version will be recorded
+     * in your `package.json` file. You can upgrade manually or using `pnpm
+     * add/update`. If you wish to specify a version range use this syntax:
      * `module@^7`.
      */
     addDevDeps(...deps: string[]): void;
@@ -593,9 +593,9 @@ export declare class NodePackage extends Component {
      * your code against the minimum version required from your consumers.
      *
      * @param deps Names modules to install. By default, the the dependency will
-     * be installed in the next `npx projen` run and the version will be recorded
-     * in your `package.json` file. You can upgrade manually or using `yarn
-     * add/upgrade`. If you wish to specify a version range use this syntax:
+     * be installed in the next `pnpm projen` run and the version will be recorded
+     * in your `package.json` file. You can upgrade manually or using `pnpm
+     * add/update`. If you wish to specify a version range use this syntax:
      * `module@^7`.
      */
     addPeerDeps(...deps: string[]): void;
@@ -606,9 +606,9 @@ export declare class NodePackage extends Component {
      * `bundledDependencies` section of your `package.json`.
      *
      * @param deps Names modules to install. By default, the the dependency will
-     * be installed in the next `npx projen` run and the version will be recorded
-     * in your `package.json` file. You can upgrade manually or using `yarn
-     * add/upgrade`. If you wish to specify a version range use this syntax:
+     * be installed in the next `pnpm projen` run and the version will be recorded
+     * in your `package.json` file. You can upgrade manually or using `pnpm
+     * add/update`. If you wish to specify a version range use this syntax:
      * `module@^7`.
      */
     addBundledDeps(...deps: string[]): void;
@@ -669,7 +669,7 @@ export declare class NodePackage extends Component {
      */
     get installCommand(): string;
     /**
-     * Renders `yarn install` or `npm install` with lockfile update (not frozen)
+     * Renders `pnpm install` or `npm install` with lockfile update (not frozen)
      */
     get installAndUpdateLockfileCommand(): string;
     /**