eslint_d.js VS themecreator

After migration from coc to native lsp I experienced slower formatting. However, https://github.com/mantoni/eslint_d.js/ and https://github.com/mikew/prettier_d_slim solved the issue for me.

https://github.com/mantoni/eslint_d.js/issues/152#issuecomment-782257649

[SOLVED] Thank you all! I am attempting to make a custom theme using ThemeCreator, but this problem also appears for other custom themes that aren't installed in bare Emacs, but come from the color-theme-modern package. For these themes, and the one I created and installed from a local file, the colors appear to be broken in my terminal (bash via GNOME terminal on Manjaro + GNOME). Using TERM="xterm-256color" changes nothing, and in fact using TERM="xterm" is slightly better (in the sense that it's closer to the original theme). I suspect something fishy is happening though, as the real issues set in after I agree to run the Lisp from these themes. For example, let's say I'm running wombat theme but want to switch to taylor. Everything looks fine (or what I consider fine) in wombat, I navigate up to taylor and hit enter, the colors change to something that looks nice but probably isn't Taylor (maybe ⠀some previous selection that isn't wombat), but then as soon as I allow the Lisp from Taylor to run, I get an absolutely horrible scheme that is almost unreadable. All appears well in GUI Emacs, but I am not interested in using that unfortunately. I have also tried other, more esoteric settings for the TERM variable, but to no avail. Any help would be greatly appreciated!

I am attempting to create a custom theme using ThemeCreator, but this problem also appears for other custom themes that aren't installed in bare Emacs, but come from the color-theme-modern package.