removed from npm? about eslint-plugin-semistandard-react

[adamelliotfields]

Hey @jacobleesinger , I actually was just cleaning up my public NPM profile and did remove it. It had no dependencies and virtually no weekly downloads.

I suppose you could copy the config from GitHub (which I'm probably going to delete soon), but I'd really recommend using something like Airbnb (especially since none of my packages on NPM have been updated in 4 years).

[jacobleesinger]

can I fork the repo and republish the package? This is blocking some fairly urgent changes I need to deploy and I'd really rather not have to redo my linting setup to do so.

[adamelliotfields]

If I were in your shoes, I would just remove the lint script from whatever CI you're using just to get your builds to pass.

I say that because when you unpublish a package from NPM, you cannot publish a new version for 24 hours.

Edit: You can just update your package.json to pull these 2 packages from GitHub instead of NPM.

{
  "devDependencies": {
-   "eslint-config-semistandard-react": "^4.2.0",
-  	"eslint-plugin-semistandard-react": "^4.1.0"
+   "eslint-config-semistandard-react": "github:adamelliotfields/eslint-config-semistandard-react#v4.2.0",
+   "eslint-plugin-semistandard-react": "github:adamelliotfields/eslint-plugin-semistandard-react#v4.1.0"
  }
}

I'm going to publish a patch version to NPM later this afternoon with a deprecation message and instructions on how to migrate to the official config.

[adamelliotfields]

Just published v4.1.1 of the plugin and v4.2.1 of the config to NPM with a deprecation message. You might have to update your package-lock.json so it downloads the latest versions of each, since the other versions no longer exist.