GITHUB . COM {
}
Detected CMS Systems:
- Wordpress (2 occurrences)
Title:
(parser) Deprecate `useBR` · Issue #2559 · highlightjs/highlight.js
Description:
From isagalaev in #2529: I was walking by, and while I didn't read through the entire thing I wanted to say this. There were a few features added to the core at users' requests when it was ...
Website Age:
17 years and 8 months (reg. 2007-10-09).
Matching Content Categories {📚}
- Mobile Technology & AI
- Technology & Computing
- Video & Online Content
Content Management System {📝}
What CMS is github.com built with?
Github.com is built with WORDPRESS.
Traffic Estimate {📈}
What is the average monthly size of github.com audience?
🚀🌠 Tremendous Traffic: 10M - 20M visitors per month
Based on our best estimate, this website will receive around 13,918,967 visitors per month in the current month.
check SE Ranking
check Ahrefs
check Similarweb
check Ubersuggest
check Semrush
How Does Github.com Make Money? {💸}
Subscription Packages {💳}
We've located a dedicated page on github.com that might include details about subscription plans or recurring payments. We identified it based on the word pricing in one of its internal links. Below, you'll find additional estimates for its monthly recurring revenues.How Much Does Github.com Make? {💰}
Subscription Packages {💳}
Prices on github.com are in US Dollars ($).
They range from $4.00/month to $21.00/month.
We estimate that the site has approximately 6,945,396 paying customers.
The estimated monthly recurring revenue (MRR) is $29,170,665.
The estimated annual recurring revenues (ARR) are $350,047,976.
Wordpress Themes and Plugins {🎨}
What WordPress theme does this site use?
It is strange but we were not able to detect any theme on the page.
What WordPress plugins does this website use?
It is strange but we were not able to detect any plugins on the page.
Keywords {🔍}
joshgoebel, usebr, parser, deprecate, plugin, mentioned, sign, code, issue, added, enhancement, requests, projects, closed, remove, language, html, pre, things, tags, navigation, open, highlightjs, pull, actions, security, thing, core, cases, path, precode, element, translate, beforehighlightblock, afterhighlightblock, feature, discusspropose, proposal, featuredirection, milestone, egorrogov, commented, changed, plugins, github, type, footer, skip, content, menu,
Topics {✒️}
multi-line code blocks completed joshgoebel mentioned css white-space comment metadata assignees remove corner cases users' requests v11 remove usebr pre/code tags type projects projects milestone 11 highlightjs / highlight joshgoebel closed open features added pre/code html merging move usebr special cases v11 todolist issue precise recommendation post-processing 100% complete relationships personal information plugin api entire thing code github deprecate language prefixes ugly things blessed path innerhtml = block usebr tags 0 closed js parser enhancement plugins plugin pre pre /blessed path thing innerhtml brplugin changed language
Payment Methods {📊}
- Braintree
Questions {❓}
- Already have an account?
- Provide plugin?
Schema {🗺️}
DiscussionForumPosting:
context:https://schema.org
headline:(parser) Deprecate `useBR`
articleBody:From isagalaev in #2529:
> I was walking by, and while I didn't read through the entire thing I wanted to say this. There were a few features added to the core at users' requests when it was all small an nimble. These days I would say it makes much more sense to be opinionated and remove corner cases like useBR, tabWidth and several different spellings of "lang-", "language-" as language prefixes in the class name (as far as I remember there is a very precise recommendation in HTML5 to use "language-"). Everyone with special cases would be expected to do pre- or post-processing.
Very early on we were perhaps a bit too open and allowed some things to slip into core that perhaps should not have - and today they are also things that could easily be handled with our new plugin API.
`useBR` is a messy one for me, so I'm picking on it first. I think it's obvious the "best/blessed" path for using HLJS is with pre/code tags... that gives you the best chance of preserving your code in markup without doing ugly things like inserting HTML line breaks in it in the first place. Those who really need to use a different element and need to do `<BR>` > `\n` translate can simply use a plugin to accomplish the same thing in the future.
- [x] v10.1 Deprecate `useBR`
- [x] Provide plugin?
- [x] v11 Remove `useBR`
---
**Consider:** You probably don't want a plugin at all and should consider just using CSS `white-space: pre` if you really need your code in tags other than `<pre>`.
Plugin:
```js
const brPlugin = {
"before:highlightBlock": ({ block }) => {
block.innerHTML = block.innerHTML.replace(/\n/g, '').replace(/<br[ /]*>/g, '\n');
},
"after:highlightBlock": ({ result }) => {
result.value = result.value.replace(/\n/g, "<br>");
}
};
// how to use it
hljs.addPlugin(brPlugin);
```
author:
url:https://github.com/joshgoebel
type:Person
name:joshgoebel
datePublished:2020-05-15T23:34:45.000Z
interactionStatistic:
type:InteractionCounter
interactionType:https://schema.org/CommentAction
userInteractionCount:3
url:https://github.com/2559/highlight.js/issues/2559
context:https://schema.org
headline:(parser) Deprecate `useBR`
articleBody:From isagalaev in #2529:
> I was walking by, and while I didn't read through the entire thing I wanted to say this. There were a few features added to the core at users' requests when it was all small an nimble. These days I would say it makes much more sense to be opinionated and remove corner cases like useBR, tabWidth and several different spellings of "lang-", "language-" as language prefixes in the class name (as far as I remember there is a very precise recommendation in HTML5 to use "language-"). Everyone with special cases would be expected to do pre- or post-processing.
Very early on we were perhaps a bit too open and allowed some things to slip into core that perhaps should not have - and today they are also things that could easily be handled with our new plugin API.
`useBR` is a messy one for me, so I'm picking on it first. I think it's obvious the "best/blessed" path for using HLJS is with pre/code tags... that gives you the best chance of preserving your code in markup without doing ugly things like inserting HTML line breaks in it in the first place. Those who really need to use a different element and need to do `<BR>` > `\n` translate can simply use a plugin to accomplish the same thing in the future.
- [x] v10.1 Deprecate `useBR`
- [x] Provide plugin?
- [x] v11 Remove `useBR`
---
**Consider:** You probably don't want a plugin at all and should consider just using CSS `white-space: pre` if you really need your code in tags other than `<pre>`.
Plugin:
```js
const brPlugin = {
"before:highlightBlock": ({ block }) => {
block.innerHTML = block.innerHTML.replace(/\n/g, '').replace(/<br[ /]*>/g, '\n');
},
"after:highlightBlock": ({ result }) => {
result.value = result.value.replace(/\n/g, "<br>");
}
};
// how to use it
hljs.addPlugin(brPlugin);
```
author:
url:https://github.com/joshgoebel
type:Person
name:joshgoebel
datePublished:2020-05-15T23:34:45.000Z
interactionStatistic:
type:InteractionCounter
interactionType:https://schema.org/CommentAction
userInteractionCount:3
url:https://github.com/2559/highlight.js/issues/2559
Person:
url:https://github.com/joshgoebel
name:joshgoebel
url:https://github.com/joshgoebel
name:joshgoebel
InteractionCounter:
interactionType:https://schema.org/CommentAction
userInteractionCount:3
interactionType:https://schema.org/CommentAction
userInteractionCount:3
External Links {🔗}(2)
Analytics and Tracking {📊}
- Site Verification - Google
Libraries {📚}
- Clipboard.js
- D3.js
- Lodash
Emails and Hosting {✉️}
Mail Servers:
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
Name Servers:
- dns1.p08.nsone.net
- dns2.p08.nsone.net
- dns3.p08.nsone.net
- dns4.p08.nsone.net
- ns-1283.awsdns-32.org
- ns-1707.awsdns-21.co.uk
- ns-421.awsdns-52.com
- ns-520.awsdns-01.net