nordtheme.vim/.npmrc
Sven Greb e5b59d8b5a nordtheme organization migration
As part of the "Northern Post - The state and roadmap of Nord" [1]
announcement, this repository will be migrated to the `nordtheme` GitHub
organization [2].
This issue is a task of the nordtheme/nord#185 [3] epic (tasklist [4]).

[1]: https://github.com/orgs/nordtheme/discussions/183
[2]: https://github.com/nordtheme
[3]: https://github.com/nordtheme/nord/issues/185
[4]: https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists

GH-335
2023-03-07 22:45:11 +01:00

19 lines
1 KiB
Plaintext

# Copyright (c) 2016-present Sven Greb <development@svengreb.de>
# This source code is licensed under the MIT license found in the license file.
# Configurations for npm.
# See https://docs.npmjs.com/cli/v7/configuring-npm/npmrc for more details.
# Only use a lockfile for single-consumer projects, like applications, but not for multi-consumer projects like
# libraries.
# It helps to pin dependency versions, improves the security through integrity checksums, prevents possible errors
# caused by updated transitive dependencies and allows to get deterministic build results, but it can hide problems in
# multi-consumer projects when any later versions of a used dependency, or its transitive dependencies, is not
# compatible with the own project anymore.
package-lock=true
# Do not resolve to the latest minor and patch updates.
# Automatically pin dependencies to exact versions instead of resolving to latest minor and patch updates.
# This prevents possible errors caused by updated transitive dependencies.
save-exact=true