Error while compiling with DefaultConfig
See original GitHub issueHere is what i’ve done to remove the error. Remove the following line from defaultconfig file.
https://github.com/tailwindcss/tailwindcss/blob/master/stubs/defaultConfig.stub.js
...breakpoints(theme('screens')),
ERROR Failed to compile with 2 errors friendly-errors 23:38:05
ERROR in ./assets/css/tailwind.css friendly-errors 23:38:05
Module build failed (from ./node_modules/postcss-loader/src/index.js): friendly-errors 23:38:05
TypeError: breakpoints is not a function
Issue Analytics
- State:
- Created 4 years ago
- Comments:5
Top Results From Across the Web
Error while compiling with DefaultConfig · Issue #48 - GitHub
Here is what i've done to remove the error. Remove the following line from defaultconfig file.
Read more >default config not recognised in Android studio - Stack Overflow
On updating to Android studio 3.1, i am getting this error. The SourceSet 'defaultConfig' is not recognized by the Android Gradle Plugin.
Read more >Configure build variants | Android Developers
This page shows you how you can configure build variants to create different versions of your app from a single project and how...
Read more >How to resolve compatibility error when compiling android ...
SYMPTOM: After compiling android 10.8 SDK build, compatibility error occurs: "The version of this application is incompatible with one or more ...
Read more >[SOLVED] error transformDexWithDexForRelease while ...
I resolved this problem by inserting the line multiDexEnabled true in **/proj.android-studio/app/build.gradle file at defaultConfig section.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@ricardogobbosouza I got it fixed. Had to remove … in config file.
Solved it by using a newer nodejs version. Error occured with nodejs 10x, but updating to 14.x worked