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

Mangling non-main-entry-export names

Open
#892 1 comment 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
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, rollup

Research direction

Start by running the two-module example in _prepare.mjs and main.mjs through microbundle with the supplied mangle.json. Inspect how the main entry point and its re-exported names affect mangling of _stringifyCallback and _prepare; done means determining whether either name can be safely mangled and capturing the resulting behavior.

Written by the indexing model from the issue text.

Description

needs more info

Suppose I have the following two files:
_prepare.mjs

const _stringifyCallback = (_, value) => {
  if (!value.isSJS) return value;
  return `${value.type}__sjs`;
};

const _prepare = (schema) => {
  const _preparedString = JSON.stringify(schema, _stringifyCallback);
  const _preparedSchema = JSON.parse(_preparedString);

  return {
    _preparedString,
    _preparedSchema,
  };
};

export { _prepare };

and

main.mjs, which is the entry point.

import { _prepare } from './_prepare.mjs'

function a() { _prepare({}); }
function b() { /* do other stuff */ }

export { a, b }

This results in the following minification:

const _stringifyCallback=(e,r)=>r.t?`${r.type}__sjs`:r,_prepare=e=>{const r=JSON.stringify(e,_stringifyCallback);return{_:r,p:JSON.parse(r)}};function a(){_prepare({})};function b(){};export{a,b};

However, when monitoring closely _stringifyCallback could be mangled, but is not, and also _prepare could be mangled, since it is not exported from the main entry point.
Is there a way to achieve at least one of the mangling?

The following mangle.json did not change anything (I tested a lot):

{
  "minify": {
    "mangle": {
      "toplevel": true,
      "properties": true,
      "keep_fnames": false
    },
    "compress": {
      "keep_fnames": false,
      "reduce_funcs": false,
      "passes": 2
    },
    "toplevel": true
  }
}
Dominant language
JavaScript
Stars
8.1k
Forks
358
PR merge metrics
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 developit/microbundle

All issues in developit/microbundle

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.