activescott/agentmarkdown

An accurate, extensible, and fast HTML-to-markdown converter.

Hi there 👋

My name is Scott Willeke ❤️ I love spending time with family and being outside. I also love to build things - especially out of code and especially with others.

More about me at https://scott.willeke.com/about

My GitHub Stats

agentmarkdown's Issues

live example not working

main.js not being committed: https://activescott.github.io/agentmarkdown/main.js

An in-range update of @types/node is breaking the build 🚨

The devDependency @types/node was updated from 12.7.0 to 12.7.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).
• ✅ coverage/coveralls: First build on greenkeeper/@types/node-12.7.1 at 86.189% (Details).

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

The automated release is failing 🚨

🚨 The automated release from the undefined 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 undefined 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:

• Usage documentation
• Frequently Asked Questions
• Support channels

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.

---

The push permission to the Git repository is required.

semantic-release cannot push the version tag to the branch beta on remote Git repository with URL https://x-access-token:[secure]@github.com/activescott/agentmarkdown.

Please refer to the authentication configuration documentation to configure the Git credentials on your CI environment and make sure the repositoryUrl is configured with a valid Git URL.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

span before p doesn't put a linebreak before the p block

input:

<h1>heading</h1>
<span>span<span>
<p>para</p>
<span>span<span>

actual output:

# heading #

spanpara

span

expected output:

# heading #

span

para

span

blockquote

support blockquote element. References:

• https://spec.commonmark.org/0.29/#block-quotes

Deploy web example/demo to github pages

• Rebuild example distributables
• Deploy to github pages after successful build
• Update readme to link to we demo
• Only deploy on master

live example is broken

https://activescott.github.io/agentmarkdown/

Silently fails in firefox and on iOS Safari (at least)

• Fix
• Put in place a test to catch it in builds (http://casperjs.org/ test?)

[Security] Workflow cicd.yml is using vulnerable action actions/checkout

The workflow cicd.yml is referencing action actions/checkout using references v1. However this reference is missing the commit a6747255bd19d7a757dbdda8c654a9f84db19839 which may contain fix to the some vulnerability.
The vulnerability fix that is missing by actions version could be related to:
(1) CVE fix
(2) upgrade of vulnerable dependency
(3) fix to secret leak and others.
Please consider to update the reference to the action.

make rendering customizable and extensible to new elements

An in-range update of @types/puppeteer is breaking the build 🚨

The devDependency @types/puppeteer was updated from 2.0.0 to 2.0.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/puppeteer is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ✅ now: Deployment has completed (Details).
• ❌ build_and_test (12.x): There are 1 failures, 0 warnings, and 0 notices.
• ❌ build_and_test (10.x): There are 2 failures, 0 warnings, and 0 notices.

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

run regression tests on the built package before publishing

have published a package now that is broken due to files included in weird ways a couple times. need to do an npm pack and run tests on the package itself (at least a very basic test).

The automated release is failing 🚨

🚨 The automated release from the undefined 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 undefined 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:

• Usage documentation
• Frequently Asked Questions
• Support channels

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.

---

The push permission to the Git repository is required.

semantic-release cannot push the version tag to the branch master on remote Git repository with URL https://[secure]@github.com/activescott/agentmarkdown.

Please refer to the authentication configuration documentation to configure the Git credentials on your CI environment and make sure the repositoryUrl is configured with a valid Git URL.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

An in-range update of webpack-cli is breaking the build 🚨

The devDependency webpack-cli was updated from 3.3.8 to 3.3.9.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

webpack-cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ now: Deployment has failed (Details).
• ❌ test_prod_demo: null
• ✅ deploy_prod_demo: null
• ✅ deploy_package: null
• ✅ build_and_test (12.x): null
• ✅ build_and_test (10.x): null

---

Commits

The new version differs by 3 commits.

• 48c03ab chore: v3.3.9
• a1341bd Merge pull request #1078 from lneveu/fix/process-exit-hang
• ee001bd fix: use process.exitCode instead of process.exit in compilerCallback

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

images

support img element w/ alt tags

An in-range update of @typescript-eslint/eslint-plugin is breaking the build 🚨

The devDependency @typescript-eslint/eslint-plugin was updated from 2.9.0 to 2.10.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@typescript-eslint/eslint-plugin is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ✅ now: Deployment has completed (Details).
• ❌ deploy_package: There are 1 failures, 0 warnings, and 0 notices.
• ✅ build_and_test (12.x): null
• ✅ build_and_test (10.x): null

---

Release Notes for v2.10.0

2.10.0 (2019-12-02)

Bug Fixes

• eslint-plugin: [no-empty-function] add missed node types (#1271) (e9d44f5)
• eslint-plugin: [no-untyped-pub-sig] ignore set return (#1264) (6daff10)
• eslint-plugin: [no-unused-expressions] ignore directives (#1285) (ce4c803)
• eslint-plugin: [prefer-optional-chain] allow $ in identifiers (c72c3c1)
• eslint-plugin: [prefer-optional-chain] handle more cases (#1261) (57ddba3)
• eslint-plugin: [return-await] allow Any and Unknown (#1270) (ebf5e0a)
• eslint-plugin: [strict-bool-expr] allow nullish coalescing (#1275) (3b39340)
• typescript-estree: make FunctionDeclaration.body non-null (#1288) (dc73510)

Features

• eslint-plugin: [no-empty-func] private/protected construct (#1267) (3b931ac)
• eslint-plugin: [no-non-null-assert] add suggestion fixer (#1260) (e350a21)
• eslint-plugin: [no-unnec-cond] support nullish coalescing (#1148) (96ef1e7)
• eslint-plugin: [prefer-null-coal] opt for suggestion fixer (#1272) (f84eb96)
• experimental-utils: add isSpaceBetween declaration to Sou… (#1268) (f83f04b)

Commits

The new version differs by 16 commits.

• 5adb8a2 chore: publish v2.10.0
• 065393b docs(eslint-plugin): typo in the configs README (#1295)
• 96ef1e7 feat(eslint-plugin): [no-unnec-cond] support nullish coalescing (#1148)
• e350a21 feat(eslint-plugin): [no-non-null-assert] add suggestion fixer (#1260)
• ce4c803 fix(eslint-plugin): [no-unused-expressions] ignore directives (#1285)
• f84eb96 feat(eslint-plugin): [prefer-null-coal] opt for suggestion fixer (#1272)
• dc73510 fix(typescript-estree): make FunctionDeclaration.body non-null (#1288)
• 3b39340 fix(eslint-plugin): [strict-bool-expr] allow nullish coalescing (#1275)
• ebf5e0a fix(eslint-plugin): [return-await] allow Any and Unknown (#1270)
• e9d44f5 fix(eslint-plugin): [no-empty-function] add missed node types (#1271)
• 3b931ac feat(eslint-plugin): [no-empty-func] private/protected construct (#1267)
• c72c3c1 fix(eslint-plugin): [prefer-optional-chain] allow $ in identifiers
• f83f04b feat(experimental-utils): add isSpaceBetween declaration to Sou… (#1268)
• 57ddba3 fix(eslint-plugin): [prefer-optional-chain] handle more cases (#1261)
• 6daff10 fix(eslint-plugin): [no-untyped-pub-sig] ignore set return (#1264)

There are 16 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of webpack-dev-server is breaking the build 🚨

The devDependency webpack-dev-server was updated from 3.9.0 to 3.10.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

webpack-dev-server is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ✅ now: Deployment has completed (Details).
• ❌ deploy_package: There are 1 failures, 0 warnings, and 0 notices.
• ✅ build_and_test (12.x): null
• ✅ build_and_test (10.x): null

---

Release Notes for v3.10.0

3.10.0 (2019-12-18)

Features

• client: allow sock port to use location's port (sockPort: 'location') (#2341) (dc10d06)
• server: add contentBasePublicPath option (#2150) (cee700d)

Bug Fixes

• client: don't override protocol for socket connection to 127.0.0.1 (#2303) (3a31917), closes #2302
• server: respect sockPath on transportMode: 'ws' (#2310) (#2311) (e188542)
• https on chrome linux (#2330) (dc8b475)
• support webpack@5 (#2359) (8f89c01)

Commits

The new version differs by 29 commits.

• e330423 chore(release): 3.10.0
• dc8b475 fix: https on chrome linux (#2330)
• 8f89c01 fix: support webpack@5 (#2359)
• 3203688 chore(deps): update dependency url-loader to v3 (master) (#2331)
• e0c1ef0 chore(deps): update dependency webpack to ^4.41.3 (master) (#2354)
• cf82fc2 chore(deps): update dependency file-loader to v5 (#2328)
• c570222 chore(deps): update all minor dependencies (#2342)
• c16c445 chore(deps): update lock file (#2345)
• 54d222f chore(deps): update all patch dependencies (master) (patch) (#2340)
• dc10d06 feat(client): allow sock port to use location's port (#2341)
• a599f99 refactor(client): createSocketUrl to make it better unit tested (#2336)
• 5f8c575 chore(deps): update all patch dependencies (#2326)
• cee700d feat(server): add contentBasePublicPath option (#2150)
• bd6783a chore(deps): update dependency jest-junit to v10 (#2337)
• 5dfa367 chore(deps): update all minor dependencies (#2319)

There are 29 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of @typescript-eslint/eslint-plugin is breaking the build 🚨

The devDependency @typescript-eslint/eslint-plugin was updated from 2.2.0 to 2.3.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@typescript-eslint/eslint-plugin is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ build_and_test (12.x): null
• ❌ build_and_test (10.x): null

---

Release Notes for v2.3.0

2.3.0 (2019-09-16)

Bug Fixes

• typescript-estree: ImportDeclaration.specifier to Literal (#974) (2bf8231)

Features

• eslint-plugin: [explicit-member-accessibility] add support of "ignoredMethodNames" (#895) (46ee4c9)
• eslint-plugin: [no-floating-promises] Add ignoreVoid option (#796) (6a55921)
• eslint-plugin: [no-magic-numbers] add ignoreReadonlyClassProperties option (#938) (aeea4cd)
• eslint-plugin: [strict-boolean-expressions] Add allowNullable option (#794) (c713ca4)
• eslint-plugin: add no-unnecessary-condition rule (#699) (5715482)

Commits

The new version differs by 10 commits.

• fa1cf71 chore: publish v2.3.0
• 752fb31 docs(eslint-plugin): fix typo in typedef docs (#976)
• 2bf8231 fix(typescript-estree): ImportDeclaration.specifier to Literal (#974)
• aeea4cd feat(eslint-plugin): [no-magic-numbers] add ignoreReadonlyClassProperties option (#938)
• 46ee4c9 feat(eslint-plugin): [explicit-member-accessibility] add support of "ignoredMethodNames" (#895)
• 6a55921 feat(eslint-plugin): [no-floating-promises] Add ignoreVoid option (#796)
• c713ca4 feat(eslint-plugin): [strict-boolean-expressions] Add allowNullable option (#794)
• 5715482 feat(eslint-plugin): add no-unnecessary-condition rule (#699)
• b49dbfd docs(typescript-estree): document that duplicate filenames are unsupported (#957)
• b99e831 docs: financial contributors and TSLint migration updates (#970)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of webpack is breaking the build 🚨

The devDependency webpack was updated from 4.39.2 to 4.39.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ deploy_package: null
• ✅ build_and_test (12.x): null
• ✅ build_and_test (10.x): null

---

Release Notes for v4.39.3

Bugfixes

• fix a missing module in chunk caused by incorrect chunk graph generation of async chunks

Commits

The new version differs by 43 commits.

• 94929a5 4.39.3
• 6bf1868 Merge pull request #9635 from webpack/bugfix/9634
• 83dd295 fixes #9634
• 54519bd Merge pull request #9630 from webpack/dependabot/npm_and_yarn/eslint-utils-1.4.2
• aa8d930 chore(deps): bump eslint-utils from 1.3.1 to 1.4.2
• b16ca50 Merge pull request #9603 from noscripter/patch-1
• 0601b12 Merge pull request #9623 from webpack/dependabot/npm_and_yarn/less-3.10.3
• d56b9f8 chore(deps-dev): bump less from 3.10.2 to 3.10.3
• 9dc49cf Merge pull request #9613 from shaodahong/optimize-eslint
• 85421cd improve linting performance
• 94d1768 resolve linting issues in test/helpers
• 7ee8ca3 optimize code-lint config
• 9b02c19 Merge pull request #9617 from webpack/dependabot/npm_and_yarn/eslint-plugin-jest-22.15.2
• 45622a4 Merge pull request #9616 from webpack/dependabot/npm_and_yarn/less-3.10.2
• 3c252ff Merge pull request #9608 from webpack/dependabot/npm_and_yarn/types/node-10.14.16

There are 43 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of eslint-config-prettier is breaking the build 🚨

The devDependency eslint-config-prettier was updated from 6.7.0 to 6.8.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-config-prettier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ✅ now: Deployment has completed (Details).
• ❌ deploy_package: There are 2 failures, 0 warnings, and 0 notices.
• ✅ build_and_test (12.x): null
• ✅ build_and_test (10.x): null

---

Commits

The new version differs by 3 commits.

• d6bf4c0 eslint-config-prettier v6.8.0
• f2736c2 Update npm packages
• 4d16ebc Disable @typescript-eslint/no-extra-semi (#129)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

fix: update node ranges to support node v13

The engines spec in the package needs to be updated to support node v13:

agentmarkdown/package.json

Line 7 in 25980f7

"node": "^10 || ^12",

[Security] Workflow cicd.yml is using vulnerable action actions/checkout

The workflow cicd.yml is referencing action actions/checkout using references v1. However this reference is missing the commit a6747255bd19d7a757dbdda8c654a9f84db19839 which may contain fix to the some vulnerability.
The vulnerability fix that is missing by actions version could be related to:
(1) CVE fix
(2) upgrade of vulnerable dependency
(3) fix to secret leak and others.
Please consider to update the reference to the action.

turn on public source view for live demo

Just set public in the now.json file: https://zeit.co/docs/v2/advanced/configuration/#public

An in-range update of @typescript-eslint/parser is breaking the build 🚨

The devDependency @typescript-eslint/parser was updated from 2.19.0 to 2.19.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@typescript-eslint/parser is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ✅ now: Deployment has completed (Details).
• ❌ build_and_test (12.x): There are 1 failures, 0 warnings, and 0 notices.
• ❌ build_and_test (10.x): There are 1 failures, 0 warnings, and 0 notices.

---

Release Notes for v2.19.1

2.19.1 (2020-02-10)

Bug Fixes

• eslint-plugin: [unbound-method] blacklist a few unbound natives (#1562) (4670aab)
• typescript-estree: ts returning wrong file with project references (#1575) (4c12dac)

Commits

The new version differs by 5 commits.

• 1c8f0df chore: publish v2.19.1
• 4c12dac fix(typescript-estree): ts returning wrong file with project references (#1575)
• e9cf734 docs(eslint-plugin): fix typo in readme
• 10d86b1 docs(eslint-plugin): [no-dupe-class-members] fix typo (#1566)
• 4670aab fix(eslint-plugin): [unbound-method] blacklist a few unbound natives (#1562)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

add fixtop navbar to cleanup live example

https://getbootstrap.com/docs/4.3/components/navbar/

put name, links to issues and github in top navbar.