You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if valid bug, or if it's your job to be the package sheriff, but I got a couple errors due to my garbage coding, because it turns out now all packages in the npm registry have a name (go figure).
Anyways, not sure if you want to emit the package eventonly if the pkg.value in question passes some basic schema (ie: has a name and version property). 🤷
The text was updated successfully, but these errors were encountered:
Not sure if valid bug, or if it's your job to be the package sheriff, but I got a couple errors due to my garbage coding, because it turns out now all packages in the npm registry have a
name
(go figure).Steps to reproduce:
Output:
Anyways, not sure if you want to emit the
package
event only if thepkg.value
in question passes some basic schema (ie: has aname
andversion
property). 🤷The text was updated successfully, but these errors were encountered: