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
{{ message }}
This repository has been archived by the owner on Jun 20, 2019. It is now read-only.
The version of this package published at https://www.npmjs.com/package/eslint-plugin-wordpress causes ESLint to throw an exception when it attempts to load the plugin due to missing files. The github/master version of this plugin installs via npm and loads properly via eslint. Would it be possible to update the npmjs version of this package? Thanks much.
The text was updated successfully, but these errors were encountered:
Apologies for the late reply @onpubcom, I'll try to get a new release published this week, I'll also update the docs on the caveats of using this work in progresseslint-plugin-wordpress version.
Thanks for the detailed reply @ntwb, sounds great. We are getting by just fine in the meantime by pulling this plugin directly via GitHub in our package.json. Looking forward to the future updates.
@onpubcom Awesome, that said there are quite a few issues with the recommended eslint-plugin-wordpress config as it currently stands 😏
I've released v1 of eslint-config-wordpress a couple of days ago, I'll release v2 maybe by the end of the week, or wait for a total of 7 days or so, and can then start focusing back here with eslint-plugin-wordpress in preparation for v3 eslint-config-wordpress and v1 eslint-plugin-wordpress releases.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The version of this package published at https://www.npmjs.com/package/eslint-plugin-wordpress causes ESLint to throw an exception when it attempts to load the plugin due to missing files. The github/master version of this plugin installs via npm and loads properly via eslint. Would it be possible to update the npmjs version of this package? Thanks much.
The text was updated successfully, but these errors were encountered: