Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ignore list for upgrade-interactive #3368

Open
kirrg001 opened this issue May 10, 2017 · 7 comments
Open

Ignore list for upgrade-interactive #3368

kirrg001 opened this issue May 10, 2017 · 7 comments

Comments

@kirrg001
Copy link

Do you want to request a feature or report a bug?

feature

What is the current behavior?
I have a couple of dependencies to ignore.
I've used GK in the past and GK offers a list to ignore dependency updates.
It would be great to have a yarn config file to add a list of dependencies to ignore, which won't show up when executing upgrade-interactive.

@bestander
Copy link
Member

We have started discussing a possibility to pass a --ignore/--filter list to upgrade/upgrade-interactive command.
I think Yarn should have something like that.
Maybe worth starting an RFC.

@nodkz
Copy link

nodkz commented Sep 28, 2017

Also it will be cool to list ignored packages in package.json something like did in greenkeeper greenkeeperio/greenkeeper#47 (comment)

{
  // ...
  "greenkeeper": {
    "ignore": ["tap-spec"]
  },
  "yarn": {
    "ignore-upgrade-interactive": ["webpack"]
  }
}

@O4epegb
Copy link

O4epegb commented Mar 6, 2019

Necroposting, but yes, that would be a nice feature to have!

@Denjul
Copy link

Denjul commented Jun 10, 2019

Would also like to have this feature in yarn

@jjoselv
Copy link

jjoselv commented Jul 7, 2021

It would be awesome to have this!

@callmeberzerker
Copy link

1.8K issues X_X

Yea I need this as well :)

@kubijo
Copy link

kubijo commented Jan 18, 2022

Not post just me too… it would be immensely useful to be able to exclude link:// type deps.
So if that case is not to be inherent in the base version, it would be nice to be able to declare the filter in a somewhat more intelligent way in the yarn config file (regexp at least)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants