Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Support multiple modules.

Open
#14 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
babel, javascript
Domain
tooling

Research direction

Start by reviewing how the plugin currently accepts its feature-flags configuration and compare it with the two import configurations shown in the issue. Done means the plugin can process both ember-metal/features and ember-metal during the migration, with coverage for the combined configuration.

Written by the indexing model from the issue text.

Description

Ember is migrating from import isEnabled from 'ember-metal/features' to import { isFeatureEnabled } from 'ember-metal';. During the transition (while the code is being updated piece by piece) it would be nice to instruct this plugin to simply process both modules. Unfortunately, that doesn't seem possible today.

One possible solution is something like:

{
  "plugins": [["feature-flags", [
    {
      "import": {
          "module": "ember-metal/features"
      },
      "features": {
          "new-feature": "disabled"
      }
    },
    {
      "import": {
          "module": "ember-metal",
          "name": "isFeatureEnabled"        
      },
      "features": {
          "new-feature": "disabled"
      }
    }
  ]]
}

@mmun - Thoughts?

Dominant language
JavaScript
Stars
56
Forks
3
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ember-cli/babel-plugin-feature-flags

All issues in ember-cli/babel-plugin-feature-flags

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.