
Security News
Browserslist-rs Gets Major Refactor, Cutting Binary Size by Over 1MB
Browserslist-rs now uses static data to reduce binary size by over 1MB, improving memory use and performance for Rust-based frontend tools.
rehype-remove-external-script-content
Advanced tools
rehype plugin to remove content of external JavaScript `script` elements
rehype plugin to remove the contents of external JavaScript <script>
s.
This package is a plugin that removes the contents of JavaScript <script>
s
that also have an src
attribute.
Scripts are supposed to be either external (with src
) or internal (with
code in them), and both is nonsensical.
You can use this plugin when you want to improve the transfer size of HTML documents.
This package is ESM only. In Node.js (version 16+), install with npm:
npm install rehype-remove-external-script-content
In Deno with esm.sh
:
import rehypeRemoveExternalScriptContent from 'https://esm.sh/rehype-remove-external-script-content@4'
In browsers with esm.sh
:
<script type="module">
import rehypeRemoveExternalScriptContent from 'https://esm.sh/rehype-remove-external-script-content@4?bundle'
</script>
On the API:
import rehypeParse from 'rehype-parse'
import rehypeRemoveExternalScriptContent from 'rehype-remove-external-script-content'
import rehypeStringify from 'rehype-stringify'
import {read} from 'to-vfile'
import {unified} from 'unified'
const file = await unified()
.use(rehypeParse)
.use(rehypeRemoveExternalScriptContent)
.use(rehypeStringify)
.process(await read('index.html'))
console.log(String(file))
On the CLI:
rehype input.html --use rehype-remove-external-script-content --output output.html
On the CLI in a config file (here a package.json
):
…
"rehype": {
"plugins": [
…
+ "rehype-remove-external-script-content",
…
]
}
…
This package exports no identifiers.
The default export is rehypeRemoveExternalScriptContent
.
unified().use(rehypeRemoveExternalScriptContent)
Remove the contents of external JavaScript <script>
s.
Transform (Transformer
).
<script src="index.js">console.log(1);</script>
<script src="index.js"></script>
HTML is parsed according to WHATWG HTML (the living standard), which is also followed by all browsers.
The syntax tree used is hast.
This package is fully typed with TypeScript.
Projects maintained by the unified collective are compatible with maintained versions of Node.js.
When we cut a new major release, we drop support for unmaintained versions of
Node.
This means we try to keep the current release line,
rehype-remove-external-script-content@^4
,
compatible with Node.js 16.
As rehype works on HTML and improper use of HTML can open you up to a
cross-site scripting (XSS) attack, use of rehype can also be unsafe.
Use rehype-sanitize
to make the tree safe.
See contributing.md
in rehypejs/.github
for ways
to get started.
See support.md
for ways to get help.
This project has a code of conduct. By interacting with this repository, organization, or community you agree to abide by its terms.
FAQs
rehype plugin to remove content of external JavaScript `script` elements
The npm package rehype-remove-external-script-content receives a total of 20,099 weekly downloads. As such, rehype-remove-external-script-content popularity was classified as popular.
We found that rehype-remove-external-script-content demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
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.
Security News
Browserslist-rs now uses static data to reduce binary size by over 1MB, improving memory use and performance for Rust-based frontend tools.
Research
Security News
Eight new malicious Firefox extensions impersonate games, steal OAuth tokens, hijack sessions, and exploit browser permissions to spy on users.
Security News
The official Go SDK for the Model Context Protocol is in development, with a stable, production-ready release expected by August 2025.