JS aggregation silently fails when file contains large sourcemap

Created on 18 May 2017, almost 8 years ago
Updated 20 August 2023, over 1 year ago

I noticed a strange problem with a JS file in development (theme js): when testing with core JS aggregation enabled, a file with 0 bytes/no content is generated - silently, without any error being thrown or logged.

When removing the JS source map contained in the JS file, the aggregation works as expected. I could even reproduce the problem with a minimal JS file containing only a logging statement plus the sourcemap, so it seems the sourcemap is the problem preventing the aggregation.

Please find attached the minimal JS file test case. Of course, this might not be a core issue as there might be other modules interfering. Also, using aggregation with JS sourcemaps is probably not a very common use case. Still, the effect is quite irritating for an important core functionality.

Can anybody reproduce this or do I need to analyze further?

🐛 Bug report
Status

Closed: duplicate

Version

11.0 🔥

Component
Asset library 

Last updated 3 days ago

No maintainer
Created by

🇨🇭Switzerland kjauslin

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024