From ae907b303a496031ceb125690c9f3f52820571c1 Mon Sep 17 00:00:00 2001
From: Lucas Savva <lucas@m1cr0man.com>
Date: Mon, 14 Jun 2021 18:17:02 +0100
Subject: [PATCH] Make warnings non-fatal

esbuild will still produce valid CSS even if
warnings are encountered. Instead of hard-failing
the build just inform the user and carry on.
---
 src/index.js | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/src/index.js b/src/index.js
index 627ad4e..91d280f 100644
--- a/src/index.js
+++ b/src/index.js
@@ -22,7 +22,7 @@ const pluginPostcssLiteral = (settings = {}) => ({
 				minify
 			});
 
-			if (result.warnings.length) return (warnings = result.warnings);
+			if (result.warnings.length) warnings = result.warnings;
 
 			return result.code;
 		};
@@ -47,15 +47,13 @@ const pluginPostcssLiteral = (settings = {}) => ({
 				.then(result => {
 					const css = parse(result.css);
 
-					if (warnings) return { warnings };
-
 					contents = contents.slice(0, start) + css + contents.slice(end);
 
 					result
 						.warnings()
 						.forEach(warn => process.stderr.write(warn.toString()));
 
-					return { contents };
+					return { contents, warnings };
 				})
 				.catch(error => {
 					if (error.name != 'CssSyntaxError') throw error;