ballercat/walt

Use production build for walt-explorer

Open

#128 opened on Jul 9, 2018

View on GitHub
 (10 comments) (2 reactions) (0 assignees)JavaScript (4,637 stars) (155 forks)batch import
good first issuehelp wantedmeta

Description

Feature Request

Build the explorer website with production settings before putting it on-line

Overview

Currently the walt-explorer is using the dev build on the website. As a result, it's a 5mb JS file. I'm pretty sure it can be reduced to a fraction of that (not to mention run significantly faster) by instructing webpack to create a production build before publishing it on the website.

Perhaps the the minification pluginsbreak the walt code, but you should be able to run webpack without them and even then it will improve the payload.

Impact

Small to medium. Mostly it's just ironic to have a bloated website for a tool to make low-level fast WASM :P

Contributor guide

Tech stack
javascriptnodejs
Domain
build systemperformance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Webpack configurationJavaScript basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
Examine the walt explorer webpack configuration (likely in webpack.config.js). The issue suggests adding mode: 'production' or using webpack's production mode. Review the comments for discussions about minification plugins that may break the code. Consider testing the production build and verifying the output size reduce significantly.