HelloZeroNet / HelloZeroNet/ZeroNet
Generate Coffeescript source maps
- Langage dominant
- JavaScript
- Étoiles
- 18.8k
- Forks
- 2.3k
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
It would be great if we could get this working for debugging the resulting JS in Firefox. [Some](http://ryanflorence.com/2012/coffeescript-source-maps/) [links](http://tarantsov.com/WorkflowThu/source-maps-with-coffeescript-and-uglify-js/).
Currently we're reading the compiler output on stdout:
``` python
compiler = subprocess.Popen(command, shell=True, stderr=subprocess.STDOUT,stdout=subprocess.PIPE)
out = compiler.stdout.read().decode("utf8")
```
So we would need to switch to using temporary files in order to get the map file out, and then making sure it gets served up - or at least stored locally. And we would also need to think about how to stop that leaking with published sites.
Any thoughts?
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
Start by tracing the Python compiler subprocess that reads compiler output from stdout. Determine how temporary files could expose the CoffeeScript source map and how the map should be served or stored. Done means Firefox can use the generated map for debugging without leaking it through published sites.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- coffeescript, python
- Domaine
- build-system, devtools
- Type d'issue
- Fonctionnalité
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100