customized path to package.json

[siddarthmishra]

Is there a possibility of adding customized path to package.json?
Let's say I have the following folder structure

First package.json (/project A) has name, scripts, dependencies and NOT version.

Second package.json (/project A/src/lib) has name, version, publishConfig and peerDependencies.

On executing standard-version in project root folder, the version needs to be updated accordingly to src/lib/package.json.
Currently it is taking root folder package.json which doesn't have version and updating the package.json by adding version key with null value.

Can it be customized to take path for package.json? If path not provided, behave as existing

[regseb]

I have a similar need for a WebExtensions that has the following tree structure:

• project/
  • package.json
  • package-lock.json
  • src/
    • manifest.json
  • test/

The manifest.json file is in the subdirectory src/. It would be nice to be able to customize Bump.pkgFiles.

[regseb]

I open a pull request (#425) to configure metadata files.

[koyre]

So are there any ways to specify the path to package that will be updated?

[phil-lgr]

I want standard-version to update only the package.json and not manifest.json..

can anybody comment on where are we at for this issue? I've had a look at the PR #372

[regseb]

@siddarthmishra – Since version 7.1.0, you can customize path to package.json. This configuration should solve your problem:

{
    "packageFiles": "src/lib/package.json",
    "bumpFiles": ["src/lib/package.json"]
}

@phil-lgr – As for siddarthmishra:

{
    "packageFiles": "package.json",
    "bumpFiles": ["package.json"]
}

@bcoe, @jbottigliero – I think this issue can be closed.

[ZaLiTHkA]

@siddarthmishra – Since version 7.1.0, you can customize path to package.json.

I just lost 3 hours of my life trying to figure out how to get this to work with a fresh install of standard-version, only to discover now that the latest version in the NPM registry is still 7.0.1.

🤦‍♂

any idea when 7.1.0 will be uploaded to npmjs.org?

[jbottigliero]

Hey All,

Sorry for the confusion folks... I'll see what I can do to help get the latest updates published on the registry. I've opened #531, for now, to try and draw attention to the issue.

As a workaround, it looks like 7.1.0 was tagged as next