feat: use createRequire instead of custom paths array #155
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
|
✔️ Deploy Preview for custom-elements-manifest-analyzer ready! 🔨 Explore the source changes: 92a494c 🔍 Inspect the deploy log: https://app.netlify.com/sites/custom-elements-manifest-analyzer/deploys/61bdd9c4b2d683000729d3f1 😎 Browse the preview: https://deploy-preview-155--custom-elements-manifest-analyzer.netlify.app |
daKmoR
force-pushed
the
feat/useCreateRequireInsteadOfCustomPathArray
branch
from
f2b3dc0
to
92a494c
Compare
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.
Suggestion to use
createRequirewith the source file instead of creating a custom path lookup array.Benefit would be
Note: "nodeModulesDepth" would need to be implemented different - I can take a stab at it if that suggestion makes sense