-
-
Notifications
You must be signed in to change notification settings - Fork 130
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
Concerto Core has the wrong package name #74
Comments
@jeromesimeon created a PR to update the package name |
Thanks @Niladri24dutta ! That's great. I would love to get @mttrbrts 's feedback on this issue since he did the refactoring into a monorepo. |
@jeromesimeon I've left some minor comments in the PR. otherwise it LGTM 👍 |
@mttrbrts Great thanks! I wanted to make sure you agree with the issue in the first place! |
A few things that should be done for this:
Once the tests pass, I'll keep an eye on the deployment to npm and can help with that if need be. |
I have made the requested changes in the PR |
Well done @Niladri24dutta ! You PR is merged now, and the corresponding package is published on npm: |
|
I think this is already fixed actually. It's probably just npm getting a little confused since we haven't had a first release yet. If you look at the latest tagged "unstable" version you have: (or in the repo itself) |
@jeromesimeon that makes sense now. is this PR elligible for hacktoberfest? |
Describe the bug
Wrong package name.
The structure of the lerna packages in the code is:
But the package name (and the published package on npmjs) for
concerto-core
is stillconcerto
. I think it would make sense to change that to avoid confusion, and align with other Accord Project packages structure/naming.Corresponding line, I believe:
concerto/packages/concerto-core/package.json
Line 2 in 9f324a3
The text was updated successfully, but these errors were encountered: