rename eslint-plugin-prebid to eslint-plugin-prebidjs
Type of change
- [X] Refactoring (no functional changes, no api changes)
Description of change
rename eslint-plugin-prebid to eslint-plugin-prebidjs to separate this local module from the vulnerable npm clone
Other information
Fixes (and should eventually close):
Doesn't this just invite someone to publish malware to the new location?
Good point... but, what could be done then? How about publishing the module within the new namespace to npm to avoid someone hijacking the namespace?
that could work, i'll keep this unmerged while we explore with npm
can you merge in master? I merged the dependency pr you did.
How about publishing the module within the new namespace to npm to avoid someone hijacking the namespace?
open to this and/or upgrading the linter. What's the next step?
How about publishing the module within the new namespace to npm to avoid someone hijacking the namespace?
open to this and/or upgrading the linter. What's the next step?
Someone needs to publish this lint-module to npm: publishing-unscoped-public-packages or publishing-scoped-public-packages
But as I'm not the author of this plugin, I'm not comfortable doing this by myself...