developit / developit/microbundle

Mangling non-main-entry-export names

Abierto
#892 1 comentario 0 reacciones 0 asignados Ver en GitHub
needs more info
Lenguaje dominante
JavaScript
Estrellas
8.1k
Forks
358
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

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
}
}
```

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
javascript, rollup
Área
build-system, tooling
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
35/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.