Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixing npm audit #84

Closed
wants to merge 1 commit into from
Closed

Fixing npm audit #84

wants to merge 1 commit into from

Conversation

wmsbill
Copy link

@wmsbill wmsbill commented Sep 25, 2019

@lucas-burdell-karmak
Copy link

I also ran into this issue recently and came here to make a PR. Glad you're ahead of me!

It looks like a snapshot file changed. I'm not familiar at all with this repo but that change doesn't look right.

@wmsbill
Copy link
Author

wmsbill commented Sep 25, 2019

I thought the same until I saw this commit 2e7f73f

@lucas-burdell-karmak
Copy link

I thought the same until I saw this commit 2e7f73f

@ndelangen related to the commit above, is the change we see in the snapshots here not the expected behavior?

@ndelangen
Copy link
Member

Indeed, this is why I downgraded exactly

@@ -203,11 +203,9 @@ exports[`should be able to compile list 1`] = `

exports[`should be able to compile list with html tag 1`] = `
<div>
<font
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not correct, unfortunately 😢

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is fair. I'll check it out.

@ndelangen
Copy link
Member

The snapshot should stay the same.

I sunk about 2 hours into this back then, and wasn't able to upgrade without complete breaking the package.

@stof
Copy link
Contributor

stof commented Oct 15, 2019

Well, the snapshot for the test should be able to compile list with html tag expects a behavior which is not consistent with the Commonmark markdown spec. So upgrades won't ever allow it to stay unchanged (and switching markdown parser will probably not help either, as most parsers are referring to Commonmark now for interoperability).

@stof stof mentioned this pull request Oct 29, 2019
@@ -30,7 +30,7 @@
"dependencies": {
"@babel/standalone": "^7.4.5",
"he": "^1.2.0",
"marked": "^0.3.12"
"marked": "^0.7.0"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

marked already has 0.8.0 in 3 months ago
https://www.npmjs.com/package/marked

@stof
Copy link
Contributor

stof commented Mar 9, 2020

@ndelangen if the fact that there is some cases changing behavior due to the marked upgrade, maybe this could be released as a new major version of that library, if that's an issue for releasing it as a patch.

@@ -203,11 +203,9 @@ exports[`should be able to compile list 1`] = `

exports[`should be able to compile list with html tag 1`] = `
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, @stof If we remove this testcase, and upgrade, then release as a new major version, I'm ok with that.

@wmsbill wmsbill closed this May 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants