remark-remove-unused-definitions
v3.0.0
remark plugin that removes unused reference definitions from a document
0/weekUpdated 5 months agoMITUnpacked: 19.0 KB
Published by Xunnamius
npm install remark-remove-unused-definitions
remark plugin that removes unused reference definitions from a document
[![Black Lives Matter!][x-badge-blm-image]][x-badge-blm-link]
[![Last commit timestamp][x-badge-lastcommit-image]][x-badge-repo-link]
[![Codecov][x-badge-codecov-image]][x-badge-codecov-link]
[![Source license][x-badge-license-image]][x-badge-license-link]
[![Uses Semantic Release!][x-badge-semanticrelease-image]][x-badge-semanticrelease-link]
[![NPM version][x-badge-npm-image]][x-badge-npm-link]
[![Monthly Downloads][x-badge-downloads-image]][x-badge-downloads-link]
remark-remove-unused-definitions
This is a [unified][1] ([remark][2]) plugin that removes unused reference
definitions from a document. Also removes unused [GFM footnotes][3] definitions.
While you can get a similar effect by running something like the following:
``shell`
remark -o --use inline-links --use reference-links your-markdown-file.md
Such a naive approach will _destroy_ all of your carefully considered
alphanumeric reference ids (e.g. the "alphanumeric-id" in
[text][alphanumeric-id])! This plugin only elides _unused_ reference
definitions, leaving the rest intact.
---
- Install
- Usage
- Via API
- Via remark-cli
- Via unified configuration
- API
- Examples
- Related
- Appendix
- Published Package Details
- License
- Contributing and Support
- Contributors
Install
> Due to the nature of the unified ecosystem, this package is ESM only and
> cannot be require'd.
To install:
`shell`
npm install --save-dev remark-remove-unused-definitions
Usage
For maximum flexibility, there are several ways this plugin can be invoked.
$3
`typescript
import { read } from 'to-vfile';
import { remark } from 'remark';
import remarkRemoveUnusedDefs from 'remark-remove-unused-definitions';
const file = await remark()
.use(remarkRemoveUnusedDefs)
.process(await read('example.md'));
console.log(String(file));
`
$3
`shell`
remark -o --use remove-unused-definitions README.md
$3
In package.json:
`javascript`
/ … /
"remarkConfig": {
"plugins": [
"remark-remove-unused-definitions"
/ … /
]
},
/ … /
In .remarkrc.js:
`javascript`
module.exports = {
plugins: [
// …
'remove-unused-definitions'
]
};
In .remarkrc.mjs:
`javascript
import remarkRemoveUnusedDefs from 'remark-remove-unused-definitions';
export default {
plugins: [
// …
remarkRemoveUnusedDefs
]
};
`
API
Detailed interface information can be found under [docs/][x-repo-docs].
Examples
Suppose we have the following Markdown file example.md:
`markdownDocumentation
This [package][1] is [more than][2nd-half-idiom] meets the eye.
Install [remark][8]
…
[1st-half-idiom]: https://meme-link-1
[2nd-half-idiom]: https://meme-link-2
[1]: https://npm.im/some-package
[2]: #install
[3]: #usage
[4]: #api
[5]: #related
[6]: #contributing-and-support
[7]: #contributors
[8]: https://npm.im/remark
`
Then running the following JavaScript:
`typescript
import { read } from 'to-vfile';
import { remark } from 'remark';
import remarkRemoveUnusedDefs from 'remark-remove-unused-definitions';
const file = await remark()
.use(remarkRemoveUnusedDefs)
.process(await read('example.md'));
console.log(String(file));
`
Would output the following (assuming remark is [configured][4] for tight
references):
`markdownDocumentation
This [package][1] is [more than][2nd-half-idiom] meets the eye.
Install [remark][8]
…
[2nd-half-idiom]: https://meme-link-2
[1]: https://npm.im/some-package
[8]: https://npm.im/remark
`
Now all the unused definitions have been deleted. Nice!
Finally, notice how those numeric reference definition ids are not contiguous:
instead of [1] and [2] it's [1] and [8]. Luckily, there exists [a remark[1]
plugin][5] that will ensure numeric reference ids flow through the document in
ascending order starting from .
Related
- [remark-reference-links][6] — transform inline links into reference-style
links.
- [remark-renumber-references][5] — contiguously renumber numeric
reference-style link ids starting from [1].
- [remark-sort-definitions][7] — logically reorder reference definitions at the
bottom of your document.
Appendix
Further documentation can be found under [docs/][x-repo-docs].
$3
This is an [ESM-only package][x-pkg-esm-wine] built by Babel for use in Node.js
versions that are not end-of-life. For TypeScript users, this package supports
both "Node10" and "Node16" module resolution strategies.
Expand details
That means ESM source will load this package via import { ... } from ... orawait import(...) and CJS source will load this package via dynamicimport(). This has several benefits, the foremost being: less code
shipped/smaller package size, avoiding [dual package
hazard][x-pkg-dual-package-hazard] entirely, distributables are not
packed/bundled/uglified, and a drastically less complex build process.
The glaring downside, which may or may not be relevant, is that CJS consumers
cannot require() this package and can only use import() in an asynchronous
context. This means, in effect, CJS consumers may not be able to use this
package at all.
Each entry point (i.e. ENTRY) in [package.json'sexports[ENTRY]][x-repo-package-json] object includes one or more [exportexports[ENTRY].types
conditions][x-pkg-exports-conditions]. These entries may or may not include: an
[][x-pkg-exports-types-key] condition pointing to a typeexports[ENTRY].module
declaration file for TypeScript and IDEs, a
[][x-pkg-exports-module-key] condition pointing toexports[ENTRY].node
(usually ESM) source for Webpack/Rollup, a and/orexports[ENTRY].default condition pointing to (usually CJS2) source for Node.jsrequire/import and for browsers and other environments, and [other
conditions][x-pkg-exports-conditions] not enumerated here. Check the
[package.json][x-repo-package-json] file to see which export conditions are
supported.
Note that, regardless of the [{ "type": "..." }][x-pkg-type] specified inpackage.json
[][x-repo-package-json], any JavaScript files written in ESM.mjs
syntax (including distributables) will always have the extension. Notepackage.json
also that [][x-repo-package-json] may include thesideEffects
[][x-pkg-side-effects-key] key, which is almost always false` for
optimal [tree shaking][x-pkg-tree-shaking] where appropriate.
$3
See [LICENSE][x-repo-license].
Contributing and Support
**[New issues][x-repo-choose-new-issue] and [pull requests][x-repo-pr-compare]
are always welcome and greatly appreciated! 🤩** Just as well, you can [star 🌟
this project][x-badge-repo-link] to let me know you found it useful! ✊🏿 Or [buy
me a beer][x-repo-sponsor], I'd appreciate it. Thank you!
See [CONTRIBUTING.md][x-repo-contributing] and [SUPPORT.md][x-repo-support] for
more information.
$3
See the [table of contributors][x-repo-contributors].
[x-badge-blm-image]: https://xunn.at/badge-blm 'Join the movement!'
[x-badge-blm-link]: https://xunn.at/donate-blm
[x-badge-codecov-image]:
https://img.shields.io/codecov/c/github/Xunnamius/unified-utils/main?style=flat-square&token=HWRIOBAAPW&flag=package.main_remark-remove-unused-definition
'Is this package well-tested?'
[x-badge-codecov-link]: https://codecov.io/gh/Xunnamius/unified-utils
[x-badge-downloads-image]:
https://img.shields.io/npm/dm/remark-remove-unused-definitions?style=flat-square
'Number of times this package has been downloaded per month'
[x-badge-downloads-link]: https://npmtrends.com/remark-remove-unused-definitions
[x-badge-lastcommit-image]:
https://img.shields.io/github/last-commit/Xunnamius/unified-utils?style=flat-square
'Latest commit timestamp'
[x-badge-license-image]:
https://img.shields.io/npm/l/remark-remove-unused-definitions?style=flat-square
"This package's source license"
[x-badge-license-link]:
https://github.com/Xunnamius/unified-utils/blob/main/LICENSE
[x-badge-npm-image]:
https://xunn.at/npm-pkg-version/remark-remove-unused-definitions
'Install this package using npm or yarn!'
[x-badge-npm-link]: https://npm.im/remark-remove-unused-definitions
[x-badge-repo-link]: https://github.com/Xunnamius/unified-utils
[x-badge-semanticrelease-image]:
https://xunn.at/badge-semantic-release
'This repo practices continuous integration and deployment!'
[x-badge-semanticrelease-link]:
https://github.com/semantic-release/semantic-release
[x-pkg-dual-package-hazard]:
https://nodejs.org/api/packages.html#dual-package-hazard
[x-pkg-esm-wine]:
https://dev.to/jakobjingleheimer/configuring-commonjs-es-modules-for-nodejs-12ed#esm-source-and-distribution
[x-pkg-exports-conditions]:
https://webpack.js.org/guides/package-exports#reference-syntax
[x-pkg-exports-module-key]:
https://webpack.js.org/guides/package-exports#providing-commonjs-and-esm-version-stateless
[x-pkg-exports-types-key]:
https://devblogs.microsoft.com/typescript/announcing-typescript-4-5-beta#packagejson-exports-imports-and-self-referencing
[x-pkg-side-effects-key]:
https://webpack.js.org/guides/tree-shaking#mark-the-file-as-side-effect-free
[x-pkg-tree-shaking]: https://webpack.js.org/guides/tree-shaking
[x-pkg-type]:
https://github.com/nodejs/node/blob/8d8e06a345043bec787e904edc9a2f5c5e9c275f/doc/api/packages.md#type
[x-repo-choose-new-issue]:
https://github.com/Xunnamius/unified-utils/issues/new/choose
[x-repo-contributing]: /CONTRIBUTING.md
[x-repo-contributors]: /README.md#contributors
[x-repo-docs]: docs
[x-repo-license]: ./LICENSE
[x-repo-package-json]: package.json
[x-repo-pr-compare]: https://github.com/Xunnamius/unified-utils/compare
[x-repo-sponsor]: https://github.com/sponsors/Xunnamius
[x-repo-support]: /.github/SUPPORT.md
[1]: https://github.com/unifiedjs/unified
[2]: https://github.com/remarkjs/remark
[3]: https://github.com/remarkjs/remark-gfm#what-is-this
[4]: /.remarkrc.mjs
[5]: /packages/remark-renumber-references
[6]: https://github.com/remarkjs/remark-reference-links
[7]: /packages/remark-sort-definitions