browserify / browserify/static-module
Some way of combining multiple transforms using static-module
- Langage dominant
- JavaScript
- Étoiles
- 75
- Forks
- 22
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
This is gonna be the most half-formed feature request I've ever posted on GitHub. Sorry!
**The problem to solve:** Since `static-module` works by parsing into an AST, transforming, and code-generating, it has a pretty significant overhead associated with it. For example: I have a script build using Browserify which takes about 8 seconds, where <2 seconds are spent compiling (TypeScript) and the remaining >6 seconds are spent in various transforms using `static-module` (`brfs` and `varlessify` (I wrote the latter)). I want to add another `static-module`-based transform, but I hesitate to add another 3 seconds to my incremental build time!
**Imagine a world** where multiple transforms using `static-module` could be combined into a single transform, thus significantly decreasing the performance impact. The source would only have to get parsed into an AST once! This would open the door to scalable use of tons of compile-time transformations. I'm not sure what the API for this would look like, but I have an inkling that it could _possibly_ be done entirely within `static-module` without requiring any changes to downstream modules like `brfs`, perhaps by returning an extra property on the result of `staticModule()`.
``` js
// a bunch of different transforms, more realistically pulled in separately from different modules
var brfs = staticModule({ { fs: ... }, ... });
var brfoo = staticModule({ { foo: ... }, ...});
var brbar = staticModule({ { bar: ... }, ...});
// combine them all
var massiveTransform = staticModule.combine(brfs, brfoo, brbar);
```
Thoughts?
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
Commencez par examiner l’API de transformation actuelle de static-module et les transforms Browserify associés mentionnés dans l’issue, notamment brfs et varlessify. Définissez une API de composition concrète qui analyse et génère chaque source une seule fois, puis mettez en place des vérifications de performances et de compatibilité montrant que les transforms combinés fonctionnent sans nécessiter de modifications en aval.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- javascript
- Domaine
- tooling
- Type d'issue
- Fonctionnalité
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100