-
Notifications
You must be signed in to change notification settings - Fork 4
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
throws on valid syntax #8
Comments
Fixed in 92a36cb . I released v0.28.1 but then also released v0.29.0 because I noticed our I've updated |
Trott
added a commit
to Trott/io.js
that referenced
this issue
Apr 25, 2022
A bug in jsdoccomment 0.28.0 forced us to pin to an earlier version. The bug has been fixed now, so we can update. Refs: es-joy/jsdoccomment#8
nodejs-github-bot
pushed a commit
to nodejs/node
that referenced
this issue
Apr 25, 2022
A bug in jsdoccomment 0.28.0 forced us to pin to an earlier version. The bug has been fixed now, so we can update. Refs: es-joy/jsdoccomment#8 PR-URL: #42857 Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com>
targos
pushed a commit
to nodejs/node
that referenced
this issue
Apr 28, 2022
A bug in jsdoccomment 0.28.0 forced us to pin to an earlier version. The bug has been fixed now, so we can update. Refs: es-joy/jsdoccomment#8 PR-URL: #42857 Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com>
juanarbol
pushed a commit
to nodejs/node
that referenced
this issue
May 31, 2022
A bug in jsdoccomment 0.28.0 forced us to pin to an earlier version. The bug has been fixed now, so we can update. Refs: es-joy/jsdoccomment#8 PR-URL: #42857 Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com>
danielleadams
pushed a commit
to nodejs/node
that referenced
this issue
Jun 27, 2022
A bug in jsdoccomment 0.28.0 forced us to pin to an earlier version. The bug has been fixed now, so we can update. Refs: es-joy/jsdoccomment#8 PR-URL: #42857 Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com>
targos
pushed a commit
to nodejs/node
that referenced
this issue
Jul 12, 2022
A bug in jsdoccomment 0.28.0 forced us to pin to an earlier version. The bug has been fixed now, so we can update. Refs: es-joy/jsdoccomment#8 PR-URL: #42857 Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com>
targos
pushed a commit
to nodejs/node
that referenced
this issue
Jul 31, 2022
A bug in jsdoccomment 0.28.0 forced us to pin to an earlier version. The bug has been fixed now, so we can update. Refs: es-joy/jsdoccomment#8 PR-URL: #42857 Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com>
guangwong
pushed a commit
to noslate-project/node
that referenced
this issue
Oct 10, 2022
A bug in jsdoccomment 0.28.0 forced us to pin to an earlier version. The bug has been fixed now, so we can update. Refs: es-joy/jsdoccomment#8 PR-URL: nodejs/node#42857 Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This bug does not exist in 0.22.1 but is in 0.28.0.
Code being processed:
Expected result is successful parsing and that's what we see in 0.22.1.
With 0.28.0, we end up with a TypeError:
References:
The text was updated successfully, but these errors were encountered: