Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

tree shaking

See original GitHub issue

I’m submitting a…

Bug report
Feature request
Documentation issue or request

Expected behavior

Support of tree-shaking with rollupjs to reduce product build size

Minimal reproduction of the problem with instructions

Environment

- generator version: 1.0.0
- node version: 8.9.4 
- npm version: 5.6.0  
- OS:  Mac

Issue Analytics

State:
Created 5 years ago
Comments:7 (3 by maintainers)

Top GitHub Comments

1reaction

sinediedcommented, Mar 27, 2018

@lakshmajim Yes, and npm run build use prod option by default so you don’t even need to specify it.

0reactions

awkward-minioncommented, Mar 27, 2018

We can close this ticket

Top Results From Across the Web

Tree shaking - MDN Web Docs Glossary

Tree shaking is a term commonly used within a JavaScript context to describe the removal of dead code. It relies on the import...

Tree Shaking - webpack

Tree shaking is a term commonly used in the JavaScript context for dead-code elimination. It relies on the static structure of ES2015 module...

Tree shaking - Wikipedia

In computing, tree shaking is a dead code elimination technique that is applied when optimizing code. Often contrasted with traditional single-library dead ...

Tree-Shaking: A Reference Guide - Smashing Magazine

Simply put, tree-shaking means removing unreachable code (also known as dead code) from a bundle. As Webpack version 3's documentation states: “ ...

Reduce JavaScript payloads with tree shaking - web.dev

Tree shaking is a form of dead code elimination. The term was popularized by Rollup, but the concept of dead code elimination has...