We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
So, i am having something odd happen with a specific node_module package.
The package exists in my package.json and in my node_modules dir
But the linter keeps puking on this.
The same thing happens on other machines even when running eslint from the cli
another odd thing is that In runtime the package is found and use though
The text was updated successfully, but these errors were encountered:
There's a bug in that package. https://unpkg.com/material-ui-superselectfield@1.1.0/package.json says "main" is lib/superSelectField.js but the filename is lib/SuperSelectField.js.
lib/superSelectField.js
lib/SuperSelectField.js
In other words, it would only work at runtime if you have a case-insensitive filesystem.
Sorry, something went wrong.
No branches or pull requests
So, i am having something odd happen with a specific node_module package.
The package exists in my package.json and in my node_modules dir
But the linter keeps puking on this.
The same thing happens on other machines even when running eslint from the cli
another odd thing is that In runtime the package is found and use though
The text was updated successfully, but these errors were encountered: