-
Notifications
You must be signed in to change notification settings - Fork 140
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
Preparing convict 6 #350
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Can you rebase |
This comment has been minimized.
This comment has been minimized.
I did the work of merging & resolving conflict in my PR#353 to save some time and let you merge the 6.0.0 with only one click :) (You just need to write the CHANGELOG.md and fix my english :') ) |
Today or tomorrow, I will improve default usage in parsing of schema and in validate (to be more user friendly) (#337), you can merge my PR but just wait my last change. |
I would like to take advantage of these break changes to rename some function. After reading the new doc of #314: https://github.com/mozilla/node-convict/pull/314/files#diff-24ac9951b3e0cda0a70e9b9877953990R306 I think @madarche Should we rename/merge We can mark load and loadFile to deprecated and remove it for convict v7 or v8. Or remove this 2 functions now to force people to read the changelog/readme of 6.0.0. |
Object-path was updated this morning but not yet published on npm. |
@A-312 I'm working on On my local repository I've changed the 4 From what I've read I think the following command should do what I want: $ npx lerna exec -- npm i I've also tried the following command, but I'm really less sure this is what I need to just update the corresponding $ npx lerna bootstrap But both commands produce the same kind of warnings:
and finish with a 1 error code. What commands should I use? Or is it a real problem? Beside, could you recommend me a project which is using lerna and has documented its commands for contributing? A beginner's guide? @A-312 could you help me please? |
@madarche It the version script tag in your package.json that cause your problem. I forget to edit. I mean this one : https://github.com/mozilla/node-convict/blob/master/assert_changelog_ready (I published my fork https://www.npmjs.com/package/blueconfig because I had to use it for my project, you can use it like example) |
Thank you @A-312, I'll use https://www.npmjs.com/package/blueconfig as a model. I'll report here soon. |
@A-312 the solution to fix the Dependency cycles detected warnings was to remove all references to I've checked-out the code of blueconfig and the Dependency cycles detected warnings are there too: node-blueconfig (master)$ npx lerna exec -- npm i
lerna notice cli v3.20.2
lerna info Executing command in 3 packages: "npm i"
lerna WARN ECYCLE Dependency cycles detected, you should fix these!
lerna WARN ECYCLE blueconfig-format-with-moment -> blueconfig -> blueconfig-format-with-moment
lerna WARN ECYCLE blueconfig-format-with-validator -> (nested cycle: blueconfig-format-with-moment -> blueconfig -> blueconfig-format-with-moment) -> blueconfig-format-with-validator
lerna WARN ECYCLE (nested cycle: blueconfig-format-with-validator -> (nested cycle: blueconfig-format-with-moment -> blueconfig -> blueconfig-format-with-moment) -> blueconfig-format-with-validator) -> (nested cycle: blueconfig-format-with-validator -> (nested cycle: blueconfig-format-with-moment -> blueconfig -> blueconfig-format-with-moment) -> blueconfig-format-with-validator) |
I think |
In blueconfig, I think I will remove |
|
convict@6.0.0 is now ready for publishing. All the points related to the use of lerna have been dealt with #368. |
@A-312, since we are preparing a new major version, are there any breaking changes that you would like to be included in 6.0.0?
The text was updated successfully, but these errors were encountered: