Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Should we use .es6 extensions? #10

Closed
kvz opened this issue Nov 17, 2015 · 2 comments
Closed

Should we use .es6 extensions? #10

kvz opened this issue Nov 17, 2015 · 2 comments
Milestone
Minimum Valuable ...

Comments

@kvz
Copy link
Member

kvz commented Nov 17, 2015

I noticed post-css used them. Is it helpful?
@kvz kvz added this to the Minimum Viable Product milestone Nov 17, 2015
@arturi
Copy link
Contributor

arturi commented Nov 17, 2015

I say no. The standard has already been renamed to ES2015, then to 16-17 or whatever, we’ll need to hire a separate person to keep up with file extensions ;) Most modern hipster projects use .js and .jsx: see https://github.com/rackt/redux, https://github.com/sindresorhus/got and others. PostCSS is an exception here.

@kvz
Copy link
Member Author

kvz commented Nov 17, 2015

Alright cool - closing this then :)

@kvz kvz closed this as completed Nov 17, 2015
@arturi arturi mentioned this issue Nov 17, 2015
Merged
8 tasks
DimaKogut added a commit to DimaKogut/uppy that referenced this issue Feb 23, 2022
@DimaKogut
Merge pull request transloadit#10 from LexPredict/dev
b70ac76 
little fix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Minimum Valuable Product
Development

No branches or pull requests
2 participants
@kvz @arturi