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

migrate to css next #48

Closed
altaywtf opened this issue Jun 9, 2016 · 2 comments
Closed

migrate to css next #48

altaywtf opened this issue Jun 9, 2016 · 2 comments
Assignees
@altaywtf
Labels
enhancement open to contributions

Comments

@altaywtf
Copy link
Contributor

altaywtf commented Jun 9, 2016

instead of having postcss plugins like precss, autoprefixer and postcss-scss separately, we can use cssnext
@batuhan
Copy link
Contributor

batuhan commented Jun 9, 2016

And that would make us future proof too I guess.

It could also have a nice side effect of fixing the css-loader bug.

@altaywtf
Copy link
Contributor Author

altaywtf commented Jun 9, 2016

@batuhan yes, definitely.

by the way, it seems like @ufukomer fixed the css-loader issue in feature/loader-fix. related pr will come tonight 🎯

@altaywtf altaywtf self-assigned this Jun 10, 2016
altaywtf added a commit that referenced this issue Jun 10, 2016
@altaywtf
Migrate to css-next
61ba268 
    - Updated: Configurations for karma, webpack dev and prod
    - Updated: Export/import method of containers
    - Updated: package.json
    - Fixed: #48
@bherila bherila mentioned this issue Jun 21, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@altaywtf altaywtf

Labels
enhancement open to contributions
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@batuhan @altaywtf