Spider build 0.3.5 doesn't distinguish between normal assets directories and flutter specific density assets directories like 2.0x and 3.0x. When we specify these directories in the configuration file, it generates assets as it is expected to be generated in normal cases. But in this case, it should not be produced at all.
A suggestion is to display warning or error in the terminal when the user tries to reference those directories.
Spider build
0.3.5doesn't distinguish between normal assets directories and flutter specific density assets directories like2.0xand3.0x. When we specify these directories in the configuration file, it generates assets as it is expected to be generated in normal cases. But in this case, it should not be produced at all.A suggestion is to display warning or error in the terminal when the user tries to reference those directories.