Feature Request: Added max line length
See original GitHub issueThis is a feature request for a max line length option. Uglify has a similar one available.
var options = {
code: true,
comments: true,
presets: [
['babel-preset-babili', { maxLineLength: 500 }]
]
};
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Feature request: extend length of version string - snapd
My snaps fail validation if the version string is > 32 characters. This limit seems arbitrary and is too short. For example, I've...
Read more >Limit line length with a sliding bar or with input - Obsidian Forum
When I switch to another theme, I have to add the code in the CSS file again, which I prefer to do with...
Read more >Request Limits <requestLimits> - Microsoft Learn
These limits include the maximum size of a request, the maximum URL length, and the maximum length for a query string. In addition,...
Read more >The anatomy of a perfect pull request | by Hugo Dias - Medium
Pull request size. It should be small. The pull request must have a maximum of 250 lines of change. Feature breaking. Whenever possible,...
Read more >RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1
Practical information systems require more functionality than simple ... The HTTP protocol does not place any a priori limit on the length of...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m curious, there’s another feature of Uglify that I personally would like to add at some point, because it tends to make debugging minified builds easier, which is setting
semicolons: false
. This means that rather than wrapping at a particular line length, uglify tries to use newlines instead of semicolons wherever possible.This means that no extra bytes are added, but lines end up being relatively short most of the time.
Would this also achieve what you’re looking for? Hard-wrapping at a line-length would either mean adding an extra byte at every newline, or require the logic to replace the closest eligible semicolon nearest the end of the line anyway.
My point is, what is shown in the diff is just a diff, it is not tied to the amount of data that is committed into a repo. In Git, you are always committing a whole new file. It may compress it for you, but it will do it however it sees fit, which is likely unaffected by how nice the Diff looks, in this specific case.