Add "main" to package.json to fix eslint issues #356
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Using eslint, I'm getting an `import/no-unresolved: Unable to resolve path to module 'vite-plugin-ruby'` when it clearly exists. Looking at [this ticket](browserify/resolve#222) I believe that is happening because there is no `main` key in the package.json. This updates the package.json to include this.
|
Thanks Lily! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description 📖
Using eslint, I'm getting an
import/no-unresolved: Unable to resolve path to module 'vite-plugin-ruby'when it clearly exists.Background 📜
Looking at this ticket I believe that is happening because there is no
mainkey in the package.json. Note that this error is not happening with thevite-rails-plugin, which does specify themainkey.The Fix 🔨
This updates the package.json to include the
mainkey.