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

Support for Meteor 3.0.1 #402

Open
67726e opened this issue Aug 22, 2024 · 6 comments
Open

Support for Meteor 3.0.1 #402

67726e opened this issue Aug 22, 2024 · 6 comments
Labels

Comments

@67726e
Copy link

67726e commented Aug 22, 2024

When adding this package to a new, Meteor 3.0.1 application it attempts to install the old 1.2.0 version of alanning:roles.

Browsing the source code, it appears there are async functions available - does this library support Meteor 3.0.1?

@67726e 67726e added the bug label Aug 22, 2024
Copy link

Thank you for submitting this issue!

We, the Members of Meteor Community Packages take every issue seriously.
Our goal is to provide long-term lifecycles for packages and keep up
with the newest changes in Meteor and the overall NodeJs/JavaScript ecosystem.

However, we contribute to these packages mostly in our free time.
Therefore, we can't guarantee your issues to be solved within certain time.

If you think this issue is trivial to solve, don't hesitate to submit
a pull request, too! We will accompany you in the process with reviews and hints
on how to get development set up.

Please also consider sponsoring the maintainers of the package.
If you don't know who is currently maintaining this package, just leave a comment
and we'll let you know

@jankapunkt
Copy link
Member

Hi @67726e can you please open your .meteor/packages file and change alanning:roles to alanning:[email protected]!?
I assume it's not considered, since still have released v4 only as RC. The v4 is supposed to be fully Meteor 3 compatible. If you have trouble with it, please let us know.

@67726e
Copy link
Author

67726e commented Aug 23, 2024

Hey @jankapunkt - that was just the fix I needed. I apologize for not checking the package.js on the feature branch 🤦

@StorytellerCZ
Copy link
Member

V4 has been released, so this should no longer be an issue.

@jankapunkt
Copy link
Member

@67726e can you confirm this works with v4 of this package?`

@StorytellerCZ
Copy link
Member

Seems to be an issue with Meteor's version resolution system. Something in there decides that it needs to get to the ancient version of that package. Happened to me on other packages as well.

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

No branches or pull requests

3 participants