https://github.com/sparticleinc/content-parser
支持在解析HTML时根据预先设置的配置文件提取内容。修改自：@postlight/parser 具体修改点在README
https://github.com/sparticleinc/content-parser
Last synced: 7 days ago
JSON representation
支持在解析HTML时根据预先设置的配置文件提取内容。修改自：@postlight/parser 具体修改点在README
- Host: GitHub
- URL: https://github.com/sparticleinc/content-parser
- Owner: sparticleinc
- License: apache-2.0
- Created: 2023-10-05T07:02:54.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2023-10-31T02:13:02.000Z (over 2 years ago)
- Last Synced: 2025-11-21T13:03:15.972Z (7 months ago)
- Language: JavaScript
- Size: 22.7 MB
- Stars: 3
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE-APACHE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
### 修改点
1. 如果对应网页没有匹配到 Extractor 的话，默认会返回所有 HTML 内容，之前是会走默认有效内容提取器。
2. Extractor 配置文件增加 content.includedPaths 字段，支持多个匹配路径，如果匹配到任意一个，就会使用该 Extractor。路径字符串会被当成正则表达式字符串。
3. Extractor 配置文件的 domain 字段现在其实是可以填任何字符串，但一般只填域名。该域名在检测配对时，只要被包含在 url 中就算匹配成功。之前是完全匹配才行。
4. 修改包名为：@sparticle/content-parser
5. 包支持导出 getExtractor，方便下游程序提前获取 Extractor，做一些其他事情。
# Postlight Parser - Extracting content from chaos
[](https://circleci.com/gh/postlight/mercury-parser) [](https://greenkeeper.io/) [![Apache License][license-apach-badge]][license-apach] [![MITC License][license-mit-badge]][license-mit]
[](https://gitter.im/postlight/mercury)
[license-apach-badge]: https://img.shields.io/badge/License-Apache%202.0-blue.svg?style=flat-square
[license-apach]: https://github.com/postlight/mercury-parser/blob/master/LICENSE-APACHE
[license-mit-badge]: https://img.shields.io/badge/License-MIT%202.0-blue.svg?style=flat-square
[license-mit]: https://github.com/postlight/mercury-parser/blob/master/LICENSE-MIT
[Postlight](https://postlight.com)'s Parser extracts the bits that humans care about from any URL you give it. That includes article content, titles, authors, published dates, excerpts, lead images, and more.
Postlight Parser powers [Postlight Reader](https://reader.postlight.com/), a browser extension that removes ads and distractions, leaving only text and images for a beautiful reading view on any site.
Postlight Parser allows you to easily create custom parsers using simple JavaScript and CSS selectors. This allows you to proactively manage parsing and migration edge cases. There are [many examples available](https://github.com/postlight/parser/tree/master/src/extractors/custom) along with [documentation](https://github.com/postlight/parser/blob/master/src/extractors/custom/README.md).
## How? Like this.
### Installation
```bash
# If you're using yarn
yarn add @postlight/parser
# If you're using npm
npm install @postlight/parser
```
### Usage
```javascript
import Parser from '@postlight/parser';
Parser.parse(url).then(result => console.log(result));
// NOTE: When used in the browser, you can omit the URL argument
// and simply run `Parser.parse()` to parse the current page.
```
The result looks like this:
```json
{
"title": "Thunder (mascot)",
"content": "...
Thunder is the stage name for the...",
"author": "Wikipedia Contributors",
"date_published": "2016-09-16T20:56:00.000Z",
"lead_image_url": null,
"dek": null,
"next_page_url": null,
"url": "https://en.wikipedia.org/wiki/Thunder_(mascot)",
"domain": "en.wikipedia.org",
"excerpt": "Thunder Thunder is the stage name for the horse who is the official live animal mascot for the Denver Broncos",
"word_count": 4677,
"direction": "ltr",
"total_pages": 1,
"rendered_pages": 1
}
```
If Parser is unable to find a field, that field will return `null`.
#### `parse()` Options
##### Content Formats
By default, Postlight Parser returns the `content` field as HTML. However, you can override this behavior by passing in options to the `parse` function, specifying whether or not to scrape all pages of an article, and what type of output to return (valid values are `'html'`, `'markdown'`, and `'text'`). For example:
```javascript
Parser.parse(url, { contentType: 'markdown' }).then(result =>
console.log(result)
);
```
This returns the the page's `content` as GitHub-flavored Markdown:
```json
"content": "...**Thunder** is the [stage name](https://en.wikipedia.org/wiki/Stage_name) for the..."
```
##### Custom Request Headers
You can include custom headers in requests by passing name-value pairs to the `parse` function as follows:
```javascript
Parser.parse(url, {
headers: {
Cookie: 'name=value; name2=value2; name3=value3',
'User-Agent':
'Mozilla/5.0 (iPhone; CPU iPhone OS 10_3_1 like Mac OS X) AppleWebKit/603.1.30 (KHTML, like Gecko) Version/10.0 Mobile/14E304 Safari/602.1',
},
}).then(result => console.log(result));
```
##### Pre-fetched HTML
You can use Postlight Parser to parse custom or pre-fetched HTML by passing an HTML string to the `parse` function as follows:
```javascript
Parser.parse(url, {
html:
'
Thunder (mascot)
Thunder is the stage name for the horse who is the official live animal mascot for the Denver Broncos
',
}).then(result => console.log(result));
```
Note that the URL argument is still supplied, in order to identify the web site and use its custom parser, if it has any, though it will not be used for fetching content.
#### The command-line parser
Postlight Parser also ships with a CLI, meaning you can use it from your command line like so:
```bash
# Install Postlight Parser globally
yarn global add @postlight/parser
# or
npm -g install @postlight/parser
# Then
postlight-parser https://postlight.com/trackchanges/mercury-goes-open-source
# Pass optional --format argument to set content type (html|markdown|text)
postlight-parser https://postlight.com/trackchanges/mercury-goes-open-source --format=markdown
# Pass optional --header.name=value arguments to include custom headers in the request
postlight-parser https://postlight.com/trackchanges/mercury-goes-open-source --header.Cookie="name=value; name2=value2; name3=value3" --header.User-Agent="Mozilla/5.0 (iPhone; CPU iPhone OS 10_3_1 like Mac OS X) AppleWebKit/603.1.30 (KHTML, like Gecko) Version/10.0 Mobile/14E304 Safari/602.1"
# Pass optional --extend argument to add a custom type to the response
postlight-parser https://postlight.com/trackchanges/mercury-goes-open-source --extend credit="p:last-child em"
# Pass optional --extend-list argument to add a custom type with multiple matches
postlight-parser https://postlight.com/trackchanges/mercury-goes-open-source --extend-list categories=".meta__tags-list a"
# Get the value of attributes by adding a pipe to --extend or --extend-list
postlight-parser https://postlight.com/trackchanges/mercury-goes-open-source --extend-list links=".body a|href"
# Pass optional --add-extractor argument to add a custom extractor at runtime.
postlight-parser https://postlight.com/trackchanges/mercury-goes-open-source --add-extractor ./src/extractors/fixtures/postlight.com/index.js
```
## License
Licensed under either of the below, at your preference:
- Apache License, Version 2.0
([LICENSE-APACHE](LICENSE-APACHE) or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license
([LICENSE-MIT](LICENSE-MIT) or http://opensource.org/licenses/MIT)
## Contributing
For details on how to contribute to Postlight Parser, including how to write a custom content extractor for any site, see [CONTRIBUTING.md](./CONTRIBUTING.md)
Unless it is explicitly stated otherwise, any contribution intentionally submitted for inclusion in the work, as defined in the Apache-2.0 license, shall be dual licensed as above without any additional terms or conditions.
---
🔬 A Labs project from your friends at [Postlight](https://postlight.com). Happy coding!