removed lib subdirectory from package.json ref #26
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
removed lib subdirectory from package.json ref from NPM package referenced main and types params.
Codecov Report
@@ Coverage Diff @@
## master #26 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 1 1
Lines 37 37
Branches 5 5
=====================================
Hits 37 37Continue to review full report at Codecov.
|
|
Thanks! I'll get this in right away. I had been reorganizing some file structure and missed this spot. Sorry! |
|
Published @ v1.1.7. |
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.
Hi,
I encountered an issue where my runtime requires weren't finding the plugin.js file.
Node was looking to postcss-nested-props/dist/lib/plugin.js as per the package.json, but the actual installed location was postcss-nested-props/dist/plugin.js.
I attempted various other machine-specific fixes:
reinitialized the containing docker container
removing and reinstalling my node_modules in the application
Neither of these resolved the issue.
I am unsure why there hasn't been any other noise on this, and I am additionally confused as my configuration was working not three days ago without the below modification.
This modification resolves this issue by pointing the main and types parameters to the appropriate issue. After this modification, node require can successfully find the plugin.js file.
Thank you for this project. Please let me know if I am errant in anything including the premise of this PR.