1602 / 1602/compound

How are js files merged?

Aperta
#621 5 commenti 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
JavaScript
Stelle
1.6k
Fork
179
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

I'm making a small change to one js file. In development mode everything is fine. However, when I push it to the server, even if a file is changed, the merged files are still getting the same name.

So even after a file is changed there production server is still serving:

```

```

So people have to clear their cache to get the new update, which is hard to explain...

In `production.coffee` I have:

```
app.enable 'merge javascripts'
```

Is there a way to less aggressively cache? Or a way to make it change the file name on every push?

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Direzione di ricerca

Look at the production.coffee configuration and the asset pipeline logic that merges and caches JavaScript files. The issue is about cache busting; investigate how the merged file name (cache_123...123.js) is generated and whether it can include a hash of the content. Check the server-side code that serves these assets and the documentation on 'merge javascripts'.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
javascript, node.js
Ambito
build-system, performance
Tipo di issue
Bug
Difficoltà
3/5
Tempo stimato
1-2 giorni
Stato di attività
Ferma
Chiarezza
Abbastanza chiara
Idoneità per principianti
45/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.