You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cordova.apache.org by er...@apache.org on 2026/02/21 07:55:26 UTC

(cordova-android) branch master updated: chore: minor changes to DEVELOPMENT.md (#1884)

This is an automated email from the ASF dual-hosted git repository.

erisu pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/cordova-android.git


The following commit(s) were added to refs/heads/master by this push:
     new edf34400 chore: minor changes to DEVELOPMENT.md (#1884)
edf34400 is described below

commit edf344008fbf47f78f7d65ea9caed7da59585011
Author: エリス <er...@users.noreply.github.com>
AuthorDate: Sat Feb 21 16:55:21 2026 +0900

    chore: minor changes to DEVELOPMENT.md (#1884)
---
 DEVELOPMENT.md | 38 ++++++++++++++++++--------------------
 1 file changed, 18 insertions(+), 20 deletions(-)

diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md
index 771d0127..ade4ca5d 100644
--- a/DEVELOPMENT.md
+++ b/DEVELOPMENT.md
@@ -95,34 +95,32 @@ cordova platform add android@nightly
 
 3. **Install dependencies:**
 
-   ```bash
-   npm install
-   ```
+    ```bash
+    npm install
+    ```
 
-   Installs all production and development dependencies required for using and developing the package.
+    Installs all production and development dependencies required for using and developing the package.
 
 4. **Update sub-dependencies:**
 
-   ```bash
-   npm update
-   ```
+    ```bash
+    npm update
+    ```
 
-   Over time, `package-lock.json` can become stale and may trigger audit warnings. `npm update` refreshes dependencies within the pinned versions.
+    Over time, `package-lock.json` can become stale and may trigger audit warnings. `npm update` refreshes dependencies within the pinned versions.
 
-   > [!NOTE]
-   > When you install the published package from the npm registry (normal usage), it does **not** include a `package-lock.json` and automatically fetches the latest compatible dependencies. Running `npm update` locally simulates this behavior.
+    Under normal circumstances, users install the published package from the npm registry, which does **not** include its own `package-lock.json`. Instead, npm resolves and installs the latest compatible dependency versions at install time, which may result in no audit warnings.
 
-5. **Generate a tarball:**
+    Running `npm update` locally can provide a more accurate representation of current npm audit results for the project.
 
-   ```bash
-   npm pack
-   ```
+5. **Generate a tarball:**
 
-   Creates a `.tgz` file that can be installed in a project via:
+    ```bash
+    npm pack
+    ```
 
-   ```bash
-   npm install /path/to/package.tgz
-   ```
+    Creates a `.tgz` tarball file in the `.asf-release` directory. This tarball file can be installed in a Cordova project via:
 
-   > [!NOTE]
-   > Tarball will be created in the `.asf-release` directory within this repository directory.
+    ```bash
+    cordova platform add /path/to/package.tgz
+    ```


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org