Use 11ty’s Compatibility API #55
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
|
Thanks @ovlb, makes sense! Can you please address the lint issues? |
|
@nunof07 Thanks. I’ve fixed the errors. I think I need to add the whole 🦉 |
|
Thank you, @ovlb , very much appreciate it! |
|
🎉 This PR is included in version 2.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Replaces
peerDependencieswith 11ty’s internal compatibility API. This allows to install the package e.g. with 2.0.0@canary, which fails using peerDependencies, as npm’s dependency API does not consider the dependency as fulfilled.See this issue for discussion and solution: 11ty/eleventy-dev-server#5