Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

storybookjs / storybook Public

Notifications You must be signed in to change notification settings
Fork 9.4k
Star 84.9k

Code
Issues 2k
Pull requests 136
Discussions
Actions
Projects 2
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Security
Insights

Core - do not mangle on production build#4838

Merged

igor-dv merged 4 commits intonextstorybookjs/storybook:nextfrom core/fix-manglestorybookjs/storybook:core/fix-mangleCopy head branch name to clipboard

Nov 24, 2018

+13-1

Conversation Commits4 (4)Checks Files changed

Commits

Commits on Nov 23, 2018

Do not use UglifyJsPlugin for production
igor-dv
committed
We should use UglifyJsPlugin on a producion build but without mangling
igor-dv
committed
Use "terser-webpack-plugin" instead of "uglifyjs-webpack-plugin" like webpack does
igor-dv
committed
Set sourceMap for minimizer.
igor-dv
committed

Footer

© 2024 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.