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

Empty output file

Open
#23 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Reproduce the reported commands using src/main.js and the foobar.min.js output target, then inspect how the tinyify plugin is invoked through the Browserify CLI. Done means identifying why the generated output is empty and confirming that a supported command produces a non-empty minified file.

Written by the indexing model from the issue text.

Description

I'm having issues trying to get this to generate a minified output file. The mentioned output file is empty. I've tried these options. None work.

browserify -p tinyify src/main.js > foobar.min.js
browserify -p tinyify src/main.js -o foobar.min.js
browserify -p tinyify -o foobar.min.js src/main.js
browserify src/main.js -p tinyify -o foobar.min.js

And they all result in an empty foobar.min.js file. What am I doing wrong?

Dominant language
JavaScript
Stars
405
Forks
14
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 browserify/tinyify

All issues in browserify/tinyify

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.