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

Support component v1

Open
  • Is something wrong?
#3 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, node.js
Domain
build-system, cli

Research direction

No files or tests are named. Start by reproducing component build -d -o <dir> -n <name> with component v1, then trace the CLI entry point and its build handling; done means the command works with component v1 or the supported process is clearly established.

Written by the indexing model from the issue text.

Description

component build -d -o <dir> -n <name> no longer works in component v1

I'm not really sure what the process is supposed to look like, I'll update if I figure something out.

Dominant language
JavaScript
Stars
70
Forks
5
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 eugeneware/decomponentify

All issues in eugeneware/decomponentify

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.