From d9447f326c9ba74e4fbaf87a7644e5b256043339 Mon Sep 17 00:00:00 2001 From: Konstantin Diachenko Date: Fri, 22 Nov 2024 01:06:52 +0530 Subject: [PATCH] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index b6e2c66..2f28b90 100644 --- a/README.md +++ b/README.md @@ -1,9 +1,9 @@ [![npm](https://img.shields.io/npm/v/use-m.svg)](https://npmjs.com/use-m) [![License](https://img.shields.io/badge/license-Unlicense-blue.svg)](https://github.com/link-foundation/use-m/blob/main/LICENSE) -# [use-m](https://github.com/link-foundation/use-m): dynamically load and import any JavaScript module +# [use-m](https://github.com/link-foundation/use-m): dynamically import any JavaScript module anywhere -`use-m` (`m` stands for `module`) is a utility for dynamically importing any JavaScript module (npm package) at runtime. +`use-m` (`m` stands for `module`) is a utility for dynamically importing any JavaScript module (npm package) at runtime anywhere (browser or server). It may be useful for standalone scripts that do not require a `package.json`. Also it may make your code portable across environments (for example it may require no changes in your code when executed in CommonJS, ES Modules and browser). You can ensure predictable behavior of your code over time by specifying the exact version to import directly in your script, similar to how versions are specified in package.json. You even can import multiple versions of the same library at the same time. You can use `use-m` when you don't want your `package.json` to be poluted with optional packages. You may keep your `package.json` with as little dependencies as needed thanks to `use-m`.