It's October again, folks!

It means Hacktoberfest is back again. Every October, this incredible event celebrates the magic of open source. It's a worldwide shindig where developers of all stripes are invited to roll up their sleeves and contribute. It’s your chance to jump in and leave your mark on the open-source universe. So, let’s get this started!

We selected a few issues that could use your brainpower and creativity. We’ll give you a little history and a dash of context, and if you need any other help or information, just shout at the Meteor team.

You can find the Meteor core team and our community on Discord, GitHub, and our forums.

Here’s the list of issues we’re excited for the community to tackle!

Improve Documentation for modern-browsers and setMinimumBrowserVersions

The modern-browsers package and the setMinimumBrowserVersions function currently lack sufficient documentation. The only references to these features are in the Changelog for version 1.7.

This gap in the docs makes it difficult for developers to understand how to configure setMinimumBrowserVersions, especially when dealing with issues like recompiling npm packages for specific browsers. The task is to add detailed explanations and examples for both modern-browsers and setMinimumBrowserVersions to the official Meteor documentation.

Fix --full Skeleton Issue in Meteor 3.0.3

The --full skeleton option no longer functions as expected, likely due to an issue with theostrio:flow-router-extra package in Meteor 3.0.3.

To reproduce the problem, simply create a new app using the --full skeleton, navigate to localhost:3000, and check the console for errors. This issue needs to be addressed to restore the functionality of the --full skeleton when setting up new Meteor apps.

Missing Types for meteor/tools in Meteor 2.x & 3.x

As part of the migration to Meteor 3, core package types should now be sourced via zodern:types, rather than DefinitelyTyped, which hasn't been updated to reflect the Meteor 3 changes. However, no types for the meteor/tools package are currently available.

Making the Meteor.user API More Clear

The Meteor.user API has a few tricky edge cases that must be addressed. The main issue here is that it can sometimes return undefined in unexpected situations. To fix this, we need to update the documentation to highlight this behavior and adjust the types to improve clarity.

Improving Documentation for the Main Meteor Function

This documentation was partially updated a while ago, but we, as maintainers, believe it could be more polished and organized. The task at hand mainly involves reorganizing the existing documentation by moving some sections to more appropriate places for better visibility and ease of use.

Accounts Collection Not Setting the Database Name Properly

With Meteor.js v2.12, we introduced a feature allowing users to name their Accounts collection. However, this feature only covers some possible cases. This issue aims to allow for full flexibility in naming collections and adding tests, ensuring the feature works across all scenarios, including edge cases.

Add the —open Flag to Meteor’s Command Line

Many modern tools like Vite and Angular support an —open command that automatically opens the user’s browser at startup. This issue proposes adding the same functionality to Meteor. The maintainers have already identified the key places in the codebase where changes are needed to implement this feature.

Making the meteor create Command More Interactive

Currently, the meteor create command is non-interactive and needs to be clarified about handling multiple flags. This issue aims to enhance the interactivity of meteor create, similar to Vite’s npm create vite@latest command. Additionally, updates to the styling and user prompts of the command are needed to improve the overall user experience.

Add TypeScript Support to the meteor create Command for Vue.js

The current meteor create command needs to handle multiple flags better. For instance, using —vue and —typescript together results in a React app with TypeScript. This is due to a lack of boilerplate for Vue + TypeScript apps, and the CLI’s inability to recognize certain flag combinations. The task is to resolve this by creating the necessary boilerplate and improving the CLI’s flag handling.

So, what do you think? Gear up and get ready to tackle these exciting challenges. Let’s make this Hacktoberfest one for the books!

If you have any questions or need clarification, feel free to contact us on GitHub.