Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in
P
purescript-gargantext
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 140
    • Issues 140
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 3
    • Merge Requests 3
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • gargantext
  • purescript-gargantext
  • Issues
  • #684

Closed
Open
Opened Jul 30, 2024 by Alfredo Di Napoli@AlfredoDiNapoli
  • Report abuse
  • New issue
Report abuse New issue

Should bundle.js be minified?

This morning I tried to open dev.sub.gargantext.org and it was taking so long I thought my connection wasn't working. However, looking at the Network tab revealed that more than two minutes were spent trying to load the bundle.js with our PureScript code:

Screenshot_2024-07-30_at_07.31.01

Eventually the issue resolved by itself (probably it was my connection being temporarily slow) but when I looked into the bundle.js code I could see how it's basically uncompressed and not minified, which make its size bigger than it should be.

Screenshot_2024-07-30_at_07.40.59

Really for production environment I cannot see of any good reason why our javascript libraries / assets shouldn't be minified, to optimise for page loading times.

Apparently spago has a --minify option, so we should try using that?

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: gargantext/purescript-gargantext#684