module-lookup-amd - npm Package Compare versions

Comparing version 8.0.0 to 8.0.1

index.js

 'use strict';
 
-const fs = require('node:fs');
-const path = require('node:path');
-const { debuglog } = require('node:util');
+const fs = require('fs');
+const path = require('path');
+const { debuglog } = require('util');
 const requirejs = require('requirejs');
@@ -7,0 +7,0 @@ const { ConfigFile } = require('requirejs-config-file');

package.json

 {
   "name": "module-lookup-amd",
-  "version": "8.0.0",
+  "version": "8.0.1",
   "description": "Resolve aliased dependency paths using a RequireJS config",
@@ -85,2 +85,3 @@ "main": "index.js",
       "unicorn/prefer-module": "off",
+      "unicorn/prefer-node-protocol": "off",
       "unicorn/prefer-string-slice": "off",
@@ -87,0 +88,0 @@ "unicorn/prefer-top-level-await": "off",

README.md

@@ -34,7 +34,7 @@ ### module-lookup-amd [![CI](https://img.shields.io/github/actions/workflow/status/dependents/node-module-lookup-amd/ci.yml?branch=main&label=CI&logo=github)](https://github.com/dependents/node-module-lookup-amd/actions/workflows/ci.yml?query=branch%3Amain) [![npm version](https://img.shields.io/npm/v/module-lookup-amd?logo=npm&logoColor=fff)](https://www.npmjs.com/package/module-lookup-amd) [![npm downloads](https://img.shields.io/npm/dm/module-lookup-amd)](https://www.npmjs.com/package/module-lookup-amd)
   as `config`. You are then required to provide a `directory` argument which is assumed to be the location where your config would have been.
-* `fileSystem`: An alternative `fs` implementation to use for filesystem interactions. Defaults to node's `fs` implementation if not supplied.
+* `fileSystem`: An alternative `fs` implementation to use for filesystem interactions. Defaults to Node.js's `fs` implementation if not supplied.
 
 ### CLI
 
-Assumes a global `-g` installation*
+Assumes a global `-g` installation
 
@@ -41,0 +41,0 @@ ```sh

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Filesystem access

Supply chain risk

Accesses the file system, and could potentially read sensitive data.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

New author

Supply chain risk

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

11325

increased by0.28%

Number of medium supply chain risk alerts

0

decreased by-100%

Worsened metrics

Number of low supply chain risk alerts

1

increased byInfinity%

No dependency changes