Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@envsa/remark-config

Package Overview
Dependencies
Maintainers
0
Versions
4
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@envsa/remark-config

Markdown and MDX linting for @envsa/shared-config.

  • 1.0.0-beta.5
  • unpublished
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
0
Maintainers
0
Weekly downloads
 
Created
Source

@envsa/remark-config

NPM Package @envsa/remark-config License: MIT

Markdown and MDX linting for @envsa/shared-config.

Overview

It's a shared Remark config for linting.

See @kitschpatrol/shared-config for the recommended single-package approach.

Setup

To use just this Remark config in isolation:

  1. Install the .npmrc in your project root. This is required for correct PNPM behavior:

    pnpm dlx @kitschpatrol/repo-config --init
    
  2. Add the package:

    pnpm add -D @kitschpatrol/remark-config
    
  3. Add the starter .remarkrc.js and files to your project root, and add any customizations you'd like:

    pnpm exec remark-config --init
    

Usage

The Remark binary should be picked up automatically by VS Code plugins.

You can call it directly, but it's recommended to use the script bundled with the shared config to invoke the remark lint rules through ESLint. The eslint-mdx plugin is used to bridge these rules into ESLint and the VS Code ESLint plugin.

Integrate with your package.json scripts as you see fit, for example:

"scripts": {
  "lint": "pnpm remark . --quiet --frail"
}

CLI

Command: remark-config

Markdown and MDX linting for @envsa/shared-config.

Usage:

remark-config [<file|glob> ...]
OptionArgumentDescription
--init
-i
Initialize by copying starter config files to your project root.
--print-config
-p
<path>Print the effective configuration at a certain path.
--help
-h
Print this help info.
--version
-v
Print the package version.

Configuration

Avoiding errors in non-git projects

The remark-validate-links looks for a git remote to validate relative link paths.

If your project is not a git repository, you will receive warning from remark via eslint:

Command failed: git remote -v
fatal: not a git repository (or any of the parent directories): .git
eslint(undefined-undefined)

To fix this, pass the repository: false option in your .remarkrc.js file:

// .remarkrc.js
import sharedConfig, { overrideRules } from '@kitschpatrol/remark-config'

const localConfig = {
  ...sharedConfig,
  plugins: overrideRules(sharedConfig.plugins, [['remarkValidateLinks', { repository: false }]]),
}

export default localConfig

License

MIT © Liam Rella

Keywords

FAQs

Package last updated on 16 Sep 2024

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc