Underlying issue :

• this plugin only handles remote urls
• postcss-import only handles local sources and only when @import statements are first and in order (following the CSS specification)

This makes it impossible to to use both plugins together without forcing a specific order of statements. Sometimes this forced order is not what is desired.

This change adds the option to store imported CSS back into an @import statement, but as a data url.

@import url(http://fonts.googleapis.com/css?family=Tangerine);

becomes :

@import url(data:text/css;base64,QGZvbnQtZmFjZSB7CiAgZm9udC1mYW1pbHk6ICdUYW5nZXJpbmUnOwogIGZvbnQtc3R5bGU6IG5vcm1hbDsKICBmb250LXdlaWdodDogNDAwOwogIHNyYzogdXJsKGh0dHA6Ly9mb250cy5nc3RhdGljLmNvbS9zL3RhbmdlcmluZS92MTcvSXVyWTZZNWpfb1NjWlpvdzRWT3hDWlpKLnR0ZikgZm9ybWF0KCd0cnVldHlwZScpOwp9Cg==);

decoded :

@font-face {
  font-family: 'Tangerine';
  font-style: normal;
  font-weight: 400;
  src: url(http://fonts.gstatic.com/s/tangerine/v17/IurY6Y5j_oScZZow4VOxCZZJ.ttf) format('truetype');
}

Combined with support for data urls in postcss-import it allows users to be more creative with their setups and plugin combinations.