hrsa's avatar
Level 5

EMFILE error on npm run dev with Tailwind installation

I have a current project that already uses sass :

let mix = require('laravel-mix');
const tailwindcss = require("tailwindcss");

mix.sass('resources/assets/sass/app.scss', 'public/css')
    .js('resources/assets/js/app.js', 'public/js')
    .sourceMaps()
    .vue()
    .extract(['datatables.net', 'formdata-polyfill', 'jquery-jscroll', 'sumoselect', 'noty', 'owl.carousel', 'jquery-validation', 'cleave.js', 'jquery-ui', 'moment', 'fullcalendar', 'toastr'])
    .version()
    .options({
    processCssUrls: false,
    autoprefixer: {
        options: {
            browsers: ['last 6 versions', ]
        }
    }
})
...

I've decided to install Tailwind to try it out. And since my app.css is being generated from app.scss file, i've added tailwind imports to app.scss:

//tailwind
@tailwind base;
@tailwind components;
@tailwind utilities;

// Configuration.
@import "../../assets-v3/sass/settings/fonts";
@import "../../assets-v3/sass/settings/variables";
@import "../../assets-v3/sass/settings/function";
@import "../../assets-v3/sass/settings/fonts";
@import "base";

//vendors npm
@import "~bootstrap/scss/bootstrap";
@import "~noty/src/noty.scss";
@import "~noty/src/themes/mint.scss";
@import "~sumoselect/sumoselect.min.css";
@import "~datatables.net-zf/css/dataTables.foundation.min.css";
@import '../../../build-v3/node_modules/vue-wysiwyg/dist/vueWysiwyg.css';
@import "../../../build-v3/node_modules/buefy/dist/buefy.css";
@import "../../assets-v3/sass/vendors/icomoon";
//layouts
@import 'global';
@import 'errors';
@import 'dashboard';
@import 'reward';
@import 'team';
...

I've used @tailwind, @require, @import - whatever the directive used, with Tailwind directives i get and Error: EMFILE: too many open files when running npm run dev. As soon as i comment the tailwind directives out -the build problems disappear.

I'm running a WIndows machine, so increasing the number of file handlers seems impossible, and i've searched the internet for numerous solutions that didn't work.

I wonder if you have ever encountered this problem, and if you managed to fix it.

0 likes
0 replies

Please or to participate in this conversation.