Should ignore css files by third parties

I have a bunch of css files in /public and /vendor and auto-prefixer is attempting to parse them. Causing the build to fail because they contain mistakes (out of my scope)

[janwerkhoven]

Because the errors occur in the vendor.css, we have no way of resolving these errors and thus we keep seeing these error appear every single time we run ember s. It’s a nuisance…

Also one could argue it’s not our responsibility to improve vendor packages. It’s up to the authors of those vendor packages to prefix and minify their CSS. Their repo is the appropriate place to add Autoprefixer, not every package consumer’s local environment. Mind the performance hits.

I’m seeing these every day and cannot fix…

autoprefixer: /Users/Jan/project/assets/vendor.css:2714:3: Gradient has outdated direction syntax. New syntax is like `to left` instead of `right`.
autoprefixer: /Users/Jan/project/assets/vendor.css:2779:3: Gradient has outdated direction syntax. New syntax is like `to left` instead of `right`.
autoprefixer: /Users/Jan/project/assets/vendor.css:2831:3: Gradient has outdated direction syntax. New syntax is like `to left` instead of `right`.
autoprefixer: /Users/Jan/project/assets/vendor.css:2882:3: Gradient has outdated direction syntax. New syntax is like `to left` instead of `right`.
autoprefixer: /Users/Jan/project/assets/vendor.css:2954:3: Gradient has outdated direction syntax. New syntax is like `to left` instead of `right`.
autoprefixer: /Users/Jan/project/assets/vendor.css:3343:3: Gradient has outdated direction syntax. New syntax is like `to left` instead of `right`.

[janwerkhoven]

What about adding it as an opt-in flag? That would avoid breaking existing projects.

  // ember-cli-build.js

  const app = new EmberApp(defaults, {
    autoprefixer: {
      vendor: false
    }
  });