Description
I would suggest to add common file extensions to every language into aliases as it will be easier for developers who want to create language detection without depending on the built-in language detection based on the file extension. For example, apache should have an alias htaccess too.
| Human Readable Name | File Extension |
|---|---|
| Apache | HTACCESS |
| JavaScript | JS |
| Markdown | MD, MKD |
| Text | TXT |
| YAML | YML, YAML |
let path = './path/to/file.js',
container = document.querySelector('pre > code');
fetch(path).then(response => {
let source = response.text(),
x = path.split('.').pop(), // Take file extension as the language name
out = hljs.highlight(x, source);
container.className += ' hljs ' + out.language;
container.innerHTML = out.value;
});Imagine someone makes a git repository viewer application and then uses highlight.js to color the code syntax in their files. This will be more robust to automatically detecting language through file extensions than by reading the file contents over and over using the available language packages until it finds the most relevant match.
This also opens up various possibilities to load language packages asynchronously based on file extensions, so the amount of data transferred will be much smaller considering that JavaScript works on the client side.