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

Specifying component name in ignore, external, exclude, noParse, etc.

Open
#27 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
tooling

Research direction

Start by tracing how the ignore, external, exclude, and noParse options handle component names versus npm modules. Compare the observed behavior with the documented or existing npm-module behavior; done means the intended handling is consistent or the limitation is clearly established.

Written by the indexing model from the issue text.

Description

This doesn't seem to work in the same way as it does for the npm modules.
Is this a known thing?

Dominant language
JavaScript
Stars
491
Forks
49
PR merge metrics
No merged PRs in 30d

Getting set up

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/debowerify

All issues in eugeneware/debowerify

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.