Lodash.min.js Download

hiplaserq.netlify.app › ▆ ▆ ▆ Lodash.min.js Download ▆ ▆ ▆

Lodash.min.js Download Average ratng: 5,7/10 8443 reviews

Rappid is a powerful and modern toolkit for building visual tools of various kinds. This documentation gives you an overview and many examples on how you can use the plugins of the Rappid toolkit to build groundbreaking applications in a fraction of a time.

-->

By Scott Addie

The LibMan CLI is a cross-platform tool that's supported everywhere .NET Core is supported.

Prerequisites

Installation

To install the LibMan CLI:

A .NET Core Global Tool is installed from the Microsoft.Web.LibraryManager.Cli NuGet package.

To install the LibMan CLI from a specific NuGet package source:

In the preceding example, a .NET Core Global Tool is installed from the local Windows machine's C:TempMicrosoft.Web.LibraryManager.Cli.1.0.94-g606058a278.nupkg file.

Usage

After successful installation of the CLI, the following command can be used:

To view the installed CLI version:

To view the available CLI commands:

The preceding command displays output similar to the following:

The following sections outline the available CLI commands.

Initialize LibMan in the project

The libman init command creates a libman.json file if one doesn't exist. The file is created with the default item template content.

Synopsis

Options

The following options are available for the libman init command:

-d --default-destination <PATH>
A path relative to the current folder. Library files are installed in this location if no destination property is defined for a library in libman.json. The <PATH> value is written to the defaultDestination property of libman.json.
-p --default-provider <PROVIDER>
The provider to use if no provider is defined for a given library. The <PROVIDER> value is written to the defaultProvider property of libman.json. Replace <PROVIDER> with one of the following values:
- cdnjs
- filesystem
- jsdelivr
- unpkg

-h --help
Show help information.
--verbosity <LEVEL>
ElcomSoft System Recovery is a product developed by Elcomsoft Co. Ltd.This site is not directly affiliated with Elcomsoft Co. Ltd.All trademarks, registered trademarks, product names and company names or logos mentioned herein are the property of their respective owners. Users of EIFT 5.30 can perform the full file system extraction and decrypt the keychain without the risks and footprint associated with third-party jailbreaks. Supported devices range from the iPhone 5s all the way up to the iPhone Xr, Xs and Xs Max if they run any version of iOS from iOS 11 through iOS 12.4 (except iOS 12.3 and 12.3.1). ElcomSoft releases a compatibility update for Elcomsoft System Recovery. Version 5.30 adds support for the new SAM encryption scheme used in Windows 10 Anniversary Update. In addition, the new release adds support for Windows Server 2016, improves built-in dictionary attacks and includes a handful of performance improvements and bug fixes. Elcomsoft System Recovery can be used to reset cached passwords to Active Directory (AD) credentials, allowing local sign-ins even if the AD domain is no longer available. MacOS Encryption. Elcomsoft System Recovery 7.20 now supports macOS computers. With Elcomsoft System Recovery, experts can now create a flash drive to boot macOS computers. ElcomSoft iOS Forensic Toolkit 5.30 118 Mb Perform physical and logical acquisition of iPhone, iPad and iPod Touch devices. Image device file system, extract device secrets (passwords, encryption keys and protected data) and decrypt the file system image. Elcomsoft password recovery.
Set the verbosity of the output. Replace <LEVEL> with one of the following values:
- quiet
- normal
- detailed

Examples

To create a libman.json file in an ASP.NET Core project:

Navigate to the project root.
Run the following command:
Type the name of the default provider, or press Enter to use the default CDNJS provider. Valid values include:
- cdnjs
- filesystem
- jsdelivr
- unpkg

A libman.json file is added to the project root with the following content:

Add library files

The libman install command downloads and installs library files into the project. A libman.json file is added if one doesn't exist. The libman.json file is modified to store configuration details for the library files.

Synopsis

Arguments

LIBRARY

The name of the library to install. This name may include version number notation (for example, @1.2.0).

Options

The following options are available for the libman install command:

-d --destination <PATH>
The location to install the library. If not specified, the default location is used. If no defaultDestination property is specified in libman.json, this option is required.
--files <FILE>
Specify the name of the file to install from the library. If not specified, all files from the library are installed. Provide one --files option per file to be installed. Relative paths are supported too. For example: --files dist/browser/signalr.js.
-p --provider <PROVIDER>
The name of the provider to use for the library acquisition. Replace <PROVIDER> with one of the following values:
- cdnjs
- filesystem
- jsdelivr
- unpkg
If not specified, the defaultProvider property in libman.json is used. If no defaultProvider property is specified in libman.json, this option is required.

-h --help
Show help information.
--verbosity <LEVEL>
Set the verbosity of the output. Replace <LEVEL> with one of the following values:
- quiet
- normal
- detailed

Examples

Consider the following libman.json file:

To install the jQuery version 3.2.1 jquery.min.js file to the wwwroot/scripts/jquery folder using the CDNJS provider:

The libman.json file resembles the following:

To install the calendar.js and calendar.css files from C:tempcontosoCalendar using the file system provider:

The following prompt appears for two reasons:

The libman.json file doesn't contain a defaultDestination property.
The libman install command doesn't contain the -d --destination option.

After accepting the default destination, the libman.json file resembles the following:

Restore library files

The libman restore command installs library files defined in libman.json. The following rules apply:

If no libman.json file exists in the project root, an error is returned.
If a library specifies a provider, the defaultProvider property in libman.json is ignored.
If a library specifies a destination, the defaultDestination property in libman.json is ignored.

Synopsis

Options

The following options are available for the libman restore command:

-h --help
Show help information.
--verbosity <LEVEL>
Set the verbosity of the output. Replace <LEVEL> with one of the following values:
- quiet
- normal
- detailed

Examples

To restore the library files defined in libman.json:

Delete library files

The libman clean command deletes library files previously restored via LibMan. Folders that become empty after this operation are deleted. The library files' associated configurations in the libraries property of libman.json aren't removed.

Synopsis

Options

The following options are available for the libman clean command:

-h --help
Show help information.
--verbosity <LEVEL>
Set the verbosity of the output. Replace <LEVEL> with one of the following values:
- quiet
- normal
- detailed

Examples

To delete library files installed via LibMan:

Uninstall library files

The libman uninstall command:

Deletes all files associated with the specified library from the destination in libman.json.
Removes the associated library configuration from libman.json.

An error occurs when:

No libman.json file exists in the project root.
The specified library doesn't exist.

If more than one library with the same name is installed, you're prompted to choose one.

Synopsis

Arguments

LIBRARY

The name of the library to uninstall. This name may include version number notation (for example, @1.2.0).

Options

The following options are available for the libman uninstall command:

-h --help
Show help information.
--verbosity <LEVEL>
Set the verbosity of the output. Replace <LEVEL> with one of the following values:
- quiet
- normal
- detailed

Examples

Consider the following libman.json file:

To uninstall jQuery, either of the following commands succeed:
To uninstall the Lodash files installed via the filesystem provider:

Update library version

The libman update command updates a library installed via LibMan to the specified version.

An error occurs when:

No libman.json file exists in the project root.
The specified library doesn't exist.

If more than one library with the same name is installed, you're prompted to choose one.

Synopsis

Arguments

LIBRARY

The name of the library to update.

Options

The following options are available for the libman update command:

-pre
Obtain the latest prerelease version of the library.
--to <VERSION>
Obtain a specific version of the library.

-h --help
Show help information.
--verbosity <LEVEL>
Set the verbosity of the output. Replace <LEVEL> with one of the following values:
- quiet
- normal
- detailed

Examples

To update jQuery to the latest version:
To update jQuery to version 3.3.1:
To update jQuery to the latest prerelease version:

Manage library cache

The libman cache command manages the LibMan library cache. The filesystem provider doesn't use the library cache.

Synopsis

Arguments

PROVIDER

Only used with the clean command. Specifies the provider cache to clean. Valid values include:

cdnjs
filesystem
jsdelivr
unpkg

Options

The following options are available for the libman cache command:

--files
List the names of files that are cached.
--libraries
List the names of libraries that are cached.

-h --help
Show help information.
--verbosity <LEVEL>
Set the verbosity of the output. Replace <LEVEL> with one of the following values:
- quiet
- normal
- detailed

Examples

To view the names of cached libraries per provider, use one of the following commands:
Output similar to the following is displayed:
To view the names of cached library files per provider:
Output similar to the following is displayed:
Notice the preceding output shows that jQuery versions 3.2.1 and 3.3.1 are cached under the CDNJS provider.
To empty the library cache for the CDNJS provider:
After emptying the CDNJS provider cache, the libman cache list command displays the following:
To empty the cache for all supported providers:
After emptying all provider caches, the libman cache list command displays the following:

Additional resources

Verify file integrity

After decompression, my uncompressed files are identical to the original ones:
MD5:
curl --silent --compressed https://raw.githubusercontent.com/lodash/lodash/4.17.10/dist/lodash.min.js --location md5sum
51a949e651144b8e525d4b2d913e6215 -
curl --silent --compressed https://minime.stephan-brumme.com/files/lodash/lodash-4.17.10.min.zopfli.js.gz md5sum
51a949e651144b8e525d4b2d913e6215 -
SHA1:
curl --silent --compressed https://raw.githubusercontent.com/lodash/lodash/4.17.10/dist/lodash.min.js --location sha1sum
2dfdedd20a6ec42794695a8c3797bd74417c4915 -
curl --silent --compressed https://minime.stephan-brumme.com/files/lodash/lodash-4.17.10.min.zopfli.js.gz sha1sum
2dfdedd20a6ec42794695a8c3797bd74417c4915 -
These CDNs send you the original file:

CDN	Size (compressed)	MD5 (uncompressed)	Timestamp
Boot	25485 bytes	51a949e651144b8e525d4b2d913e6215	(invalid)
cdnjs	24593 bytes	51a949e651144b8e525d4b2d913e6215	(invalid)

And some CDNs send you a different file:

CDN	Size (compressed)	MD5 (uncompressed)	Comment / Diff	Timestamp
unpkg	24422 bytes	19b988e43053f61d1be63a6dc5bc120e	only whitespaces differ	(invalid)

Note: only the MD5 hashes are shown to keep things simple.