Hacktoberfest is here! This is a fun and exciting event that happens every October to celebrate open source. It's a global happening that invites developers of all levels to contribute to open-source projects. Whether you're a coder, designer, writer, or just love technology, Hacktoberfest is a great opportunity to get involved and make a positive impact on the world of open source. Get ready to join the party!
In the same spirit as Jan's post, we present today a few issues that we believe could benefit from your expertise and creativity. This post will present some history and some context to the issues, and if, for some reason, the issue is not clear, you can always ping the Meteor team on GitHub.
Without further ado, here are the issues that we thought the community to work on:
The complete list of hacktoberfest issues that you can contribute can be seen here in this link
Making the Meteor.user API clearer
The issue states that Meteor.user has some edge cases that should be corrected. To solve this, adding a section about the possibility of it being undefined and updating the types is likely necessary.
Documenting the main meteor function
This issue was partially solved back in the day, but we, as the maintainers, think this documentation could be in a much better place. Following along with the issue, much of the work involves moving docs from one place to another.
Accounts not being able to correctly set their db name
In Meteor.js v2.12, we added a new feature: the ability to set whatever name you would like for your Accounts collection. However, this feature only updates some possible cases. The objective to solve this issue is not only to be able to add any name to a collection, but also to add some tests to ensure that this new feature works correctly and covers this edge case.
Add --open to our command line
Many tools have this command to open the user's browser on startup, for example, Vite and Angular. Meteor should have this feature as well. In the issue, the maintainers have listed most places where changes are necessary to implement this feature.
Make meteor create more interactive
Currently, the meteor create command is not only non-interactive but sometimes requires clarification if it accepts more than one flag when creating an app. We have created this issue to make the Meteor create command more interactive, similar to Vite's npm create vite\@latest command. Additionally, as shown in the issue, this feature must come with some updates to the styling of our command.
Add TypeScript variations to meteor create
Currently, the meteor create command does not handle a combination of commands. For example, the issue shows that if you combine --vue and --typescript, you will get a React app with TypeScript. This happens because we do not have the boilerplate to serve a Vue + TypeScript app, and the CLI does not recognize flags being used in that manner.
The issue explains possible options to implement this feature. It also includes a to-do list so that the implementer can follow along with the necessary steps to make this feature.
Our goal is to make the Meteor ecosystem even more user-friendly and feature-rich. If you have any questions or need further clarification, don't hesitate to reach out to us on GitHub. So, get ready to roll up your sleeves and dive into these exciting issues. Let's make this Hacktoberfest one to remember!
Top comments (0)