From e687e0a1647018a1566e9726c110c71a6f8fc13f Mon Sep 17 00:00:00 2001
From: Ed Morley <501702+edmorley@users.noreply.github.com>
Date: Fri, 20 Apr 2018 11:13:12 +0100
Subject: [PATCH] Adjust api_test.js no entry-point expected error message

Since webpack 4 now sets a default entry-point of `./src`, causing
the error message to change for this test. (It doesn't seem worth
creating the file to confirm it works, since from the error message
we can tell the test got far enough that Neutrino correctly didn't
complain about an explicit entry-point not being set.)
---
 packages/neutrino/test/api_test.js | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/packages/neutrino/test/api_test.js b/packages/neutrino/test/api_test.js
index 0c4ea4cbd..b949bb2b8 100644
--- a/packages/neutrino/test/api_test.js
+++ b/packages/neutrino/test/api_test.js
@@ -249,7 +249,7 @@ test('fails when trying to run() a non-registered command', async t => {
   await t.throws(Neutrino().run('non-registered').promise());
 });
 
-test('throws when trying to validate config with no entry point', async t => {
+test('throws when trying to validate config with non-existent entry point', async t => {
   const api = Neutrino();
 
   api.register('build', build);
@@ -257,5 +257,5 @@ test('throws when trying to validate config with no entry point', async t => {
 
   const [err] = await t.throws(result);
 
-  t.true(err.message.includes(`configuration misses the property 'entry'`));
+  t.true(err.includes(`Entry module not found: Error: Can't resolve './src'`));
 });