[Feature] Any chance in making this a standalone package?

[elzii]

I've almost completely moved off CoC, making nvim less of a memory hog. Long and arduos process, yet...

Literally nothing tops CoCExplorer for me. Not CHADTree, NeoTree, Oil, Fern, NetRW, nada.

Neotree comes the closest but i strongly dislike the search functionality compared to CocExplorer.

Is there something that makes this heavily dependent on CoC? Haven't perused the code heavily yet.

[weirongxu]

The core code can be reused, but some user layer areas depend on coc.nvim

• JSON configuration (based on coc-settings.json)
• Search Interactive (based on CocList)
• API: Highlight, Key mapping, Buffering list

I think part of the API can be replaced by neovim node-client, but it requires some extra adaptation code.

But you'd have to write a CocList like function to simulate the current search experience.

[elzii]

Not too huge a scope, not very small either. I'll try my hand. CocExplorer is by far the best explorer/sidebar. no new paradigms to learn, better then competitors like Neotree. Good ya either way mate. Cheers

[zhuzhzh]

I think CoC is one power framework. but it's heavy, depending on node.
coc-explorer really is the best file manager I can find. I also hope it could be one standalone plugin for vim.