Repository navigation
Use node-interpret to import configuration in various formats. - #949
Merged
Merged
Conversation
sokra
added a commit
that referenced
this pull request
Apr 7, 2015
Use node-interpret to import configuration in various formats.
Member
|
Thanks |
Contributor
|
@monder I love writing CoffeeScript. I got a question here. CLI tools like Gulp which supports CoffeeScript run without specifying a filename. As I tried, Webpack |
Contributor
Author
|
Yes. I suppose that we should have single config file format by default ( |
Contributor
|
We could also do what Gulp (liftoff) does and try to find the first matching config file without needing to pass a flag. |
Member
|
Send a PR... |
Contributor
|
Been meaning to. Will take a stab when I get some time. |
Contributor
|
Thanks @jiyinyiyong. I ended up just borrowing some logic from liftoff but that is handy. |
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
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.
This is a possible solution for #475.
Support for
*.coffeeconfiguration files is implemented using node-interpret.Other formats work as well:
P.S. Are there any tests to cover CLI?