VFile Message Daemon

Usage

LSP User

npm install -g vfmd
vfmd start
vfmd status
vfmd stop
vfmd restart

Daemon should be running beforehand.

You can also use vfmd start --attach or vfmd restart --attach not to spawn detached process.

LSP Settings

Configure following commands to your editors' LSP Client.

vfmd lsp
# You can also use stdin/stdout for communication.
# vfmd lsp --stdio

Example for vim-lsp

if executable("vfmd")
  autocmd User lsp_setup call lsp#register_server({
    \   'name': 'vfmd-lsp',
    \   'cmd': {server_info->['vfmd', 'lsp', '--stdio']},
    \   'allowlist': ['text', 'markdown', 'html'],
    \ })
endif

VFile reporter

npm install vfmd

import unified from "unified";
import markdown from "remark-parse";
import remark2rehype from "remark-rehype";
import html from "rehype-stringify";

import remark2retext from "remark-retext";
import english from "retext-english";
import indefiniteArticle from "retext-indefinite-article";
import vfile from "to-vfile";
import report from "vfile-reporter";

import { reportToDaemon } from "vfmd";

const fname = "path/to/dir/your.md";

const processor = unified()
  .use(markdown)
  .use(remark2retext, unified().use(english).use(indefiniteArticle))
  .use(remark2rehype)
  .use(html);

processor.process(vfile.readSync(fname), async (err, file) => {
  if (err) throw err;
  console.error(report(file));
  await reportToDaemon(file);
  file.extname = ".html";
  vfile.writeSync(file);
});

The automated release is failing 🚨

🚨 The automated release from the `master` branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀

lumakernel / vfile-message-daemon Goto Github PK