Skip to content

Add option to configure depdencies version range #70

Open
SkReD opened this issue Nov 25, 2022 · 0 comments
Open

Add option to configure depdencies version range #70

SkReD opened this issue Nov 25, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@SkReD
Copy link
Contributor

SkReD commented Nov 25, 2022

What is required
Possibility for configuring how dependency version range is constructed.

Given

package.json
{
  name: "@namespace/pkg",
  version: "0.0.0-stub",
  dependencies: {
    "@namespace/utils": "^0.0.0-stub"
  },
  peerDependencies: {
    "@namespace/context": "^0.0.0-stub"
  }
}

How it is now
Range for @namespace/context can be strict pkg version or ^, ~ variants. Like ^1.2.3

How i want it to be
Ranges like ^m.x, >=m <n where m is major part of dep version and n. For example if @namespace/context version is 2.3.4, then it should be possible to obtain range ^2 or >=2 <3 in published package.json

@SkReD SkReD added the enhancement New feature or request label Nov 25, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant