This repository was archived by the owner on Aug 4, 2021. It is now read-only.
Allow for relative imports to be skipped, even if the file doesn't exist #32
Conversation
This file contains hidden or 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
See rollup/rollup#532 for the explanation of the problem and the use case for skipping relative imports for files that don't exist. This pull request, in conjunction with rollup/rollup#572, resolves the issue. The revving of the rollup version in the package.json is because the new test requires rollup@^0.25.7, and npm's caret semver behavior [does not install 0.25.x when a dependency is listed at ^0.22.0](https://docs.npmjs.com/misc/semver#caret-ranges-123-025-004)
|
Ping |
|
Just seeing this, sorry for the wait – released as 1.7.0 |
|
No problem, thanks! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
See rollup/rollup#532 for the explanation of the problem and the
use case for skipping relative imports for files that don't exist.
This pull request, in conjunction with rollup/rollup#572, resolves the
issue.
The revving of the rollup version in the package.json is because the
new test requires rollup@^0.25.7, and npm's caret semver behavior
does not install 0.25.x when a dependency is listed at ^0.22.0.
The source code itself does not require rollup@^0.25.7, just the test.