question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Allow versioning/publishing of packages with ignored devDependencies

See original GitHub issue

Affected Packages

@changesets/cli @changesets/get-dependents-graph

Problem

Currently you can’t version packages with devDependencies that point at ignored packages.

devDependencies are typically only for local development of the package (from the monorepo) so we should allow you to point at ignored packages here.

For my workflow I have an internal folder in my monorepo where each internal package is prefixed with the @internal namespace. I store things like typescript configurations etc in here that most of my packages use to build but not at install time.

I want to ignore this whole namespace however I can no longer version or publish any of my packages.

Proposed solution

Add an option to allow the versioning of publishing of packages that have ignored devDependencies.

Issue Analytics

  • State:open
  • Created a year ago
  • Comments:7 (2 by maintainers)

github_iconTop GitHub Comments

2reactions
Andaristcommented, Aug 10, 2022

This sounds like a good improvement - I will try to review your PR in a couple of days 👍

1reaction
georeithcommented, Sep 13, 2022

@kachkaev looking at your error above I can’t quite follow why ignoring devDependencies isn’t enough as all of those are complaining about something that is a devDependency. Do you have the error you received when versioning after using the PR CLI?

BTW you can install a built copy of my PR without patching via https://pkg.csb.dev/changesets/changesets/commit/9da4bc95/@changesets/cli/_pkg.tgz (this is automatically generated for all changesets PRs), depending on your package manager you might need to add an extra patch to make the install work: https://github.com/yarnpkg/berry/issues/3327#issuecomment-995886724 (Might be a bit too late to be useful to you as you have diverged to your own version but may come in handy in future).

Read more comments on GitHub >

github_iconTop Results From Across the Web

Allow npm audit to ignore dev dependencies #20564 - GitHub
Currently it just makes some of my packages look vulnerable when actually there are not, and just makes me want to wipe all...
Read more >
devDependencies ignored in npm? - Stack Overflow
Yes, by default it will install the devDependencies but only for your project (devDependencies in your package.json ), not for modules in ...
Read more >
Add ability to optionally ignore dev dependencies in NPM ...
Problem to solve When running Dependency Scanning on Node.JS npm projects, Gemnasium scans all dependencies, including devDependencies.
Read more >
How to ignore dev dependencies from package-lock.json
For packages.json, it's documented that the devDependencies can be ignore with --detect.packagist.include.dev.dependencies=false.
Read more >
Adding dependencies to a package.json file - npm Docs
json file. When you (or another user) run npm install , npm will download dependencies and devDependencies that are listed in package.json that...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found