Open
Conversation
Discovered a bug where if you are watching sass files and create a new one it would throw an error that relativePath does not exist on line #147. Based on my use case this change seemed to have fixed it for me.
|
I would also like to see this fixed. It looks like the most recent merged pull request fixed the issue, but the fix has not been published to npm yet. Can we get this published? |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Discovered a bug where if you are watching sass files and create a new one it would throw an error that relativePath does not exist on line #147. Based on my use case this change seemed to have fixed it for me and I think it will for others as well.