code-input
code-input copied to clipboard
Fully customisable, editable, syntax-highlighted textareas + plugins
thanks for this awesome code. i wanted to use it for my non-code-highlighting use case involving RTL languages, and found the following issues: 1. displayed text is always left-aligned. using...
Hi, I'm just getting started with code-input and I have a question, how can I select a specific language when the autodetect plugin is registered? ```html codeInput.registerTemplate("syntax-highlighted", codeInput.templates.hljs( hljs, [...
I want to use the syntax highlighter for my editor, and see the content only with syntax highlighted and in editable mode. But currently I see it in two different...
See Actions tab and https://npmjs.org/@webcoder49/code-input ``` npm notice === Tarball Details === npm notice name: @webcoder49/code-input npm notice version: 2.4.0 npm notice filename: @webcoder49/code-input-2.4.0.tgz npm notice package size: 70.4 kB...
With the find-and-replace plugin, the up and down arrow buttons/enter key should move between all the found matches. They do so in most cases, with both highlighting engines on Chrome,...
When multiple plugins of the same class are added to a template, undesired and undocumented behaviour will often occur occur. This shouldn't occur: plugins of the same class should be...
Hello, I would like to know if it would be possible to have an auto-growing textarea containing the highlighted code working like https://css-tricks.com/the-cleanest-trick-for-autogrowing-textareas/ When I remove the height from code-input...
Typing some text to find and replace or a line number to go to can cause slowness now and make the next keystroke not be displayed for a while, so...
Document this / find a fix. This is not the case in Firefox on Linux, Chromium on Linux, Firefox on macOS, Safari on macOS, Arc on macOS.
The [code-input.js+ESM documentation](https://v2.code-input-js.org/modules-and-frameworks/hljs/esm/) doesn't make it self-explanatory. I tried using vanilla TypeScript and it initially complained until both `module` and `moduleResolution` were set to `nodeNext`. Not caused by code-input.js but...