New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add --ext
CLI flag and extensions
Node.js API option
#6617
Conversation
🦋 Changeset detectedLatest commit: a77ac8d The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
7c242be
to
d37b8b0
Compare
1345fa9
to
2e4984f
Compare
2e4984f
to
697dc35
Compare
d6fb067
to
57c950b
Compare
2495867
to
81a4e17
Compare
978828f
to
0173c41
Compare
6677b12
to
20e50d2
Compare
d72ec44
to
9046a08
Compare
Can the leading dot be made optional, so that |
I guess we could. If we do add it we would need a new test and documentation update(s).
|
bf85689
to
b1292c7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the hard work. The behavior seems no problems.
I've suggested a few comments for a bit of improvement and maintainability. Please consider addressing them.
Closes #6689
--ext
flag'.css'
defaultextensions
Node.jsextendsextensions
extends
.
fixturePath
test utilI used ESLint as a reference.
see #6617 (comment)
I am not planning to cover RFC20 in this first iteration, let's keep it simple.
related upstream issue: sindresorhus/meow#164