Every new change

node_modules/eslint/messages/all-files-ignored.txt

@@ -0,0 +1,8 @@
+You are linting "<%= pattern %>", but all of the files matching the glob pattern "<%= pattern %>" are ignored.
+
+If you don't want to lint these files, remove the pattern "<%= pattern %>" from the list of arguments passed to ESLint.
+
+If you do want to lint these files, try the following solutions:
+
+* Check your .eslintignore file, or the eslintIgnore property in package.json, to ensure that the files are not configured to be ignored.
+* Explicitly list the files from this glob that you'd like to lint on the command-line, rather than providing a glob as an argument.

node_modules/eslint/messages/extend-config-missing.txt

@@ -0,0 +1,5 @@
+ESLint couldn't find the config "<%- configName %>" to extend from. Please check that the name of the config is correct.
+
+The config "<%- configName %>" was referenced from the config file in "<%- importerName %>".
+
+If you still have problems, please stop by https://gitter.im/eslint/eslint to chat with the team.

node_modules/eslint/messages/failed-to-read-json.txt

@@ -0,0 +1,3 @@
+Failed to read JSON file at <%= path %>:
+
+<%= message %>

node_modules/eslint/messages/file-not-found.txt

@@ -0,0 +1,2 @@
+No files matching the pattern "<%= pattern %>"<% if (globDisabled) { %> (with disabling globs)<% } %> were found.
+Please check for typing mistakes in the pattern.

node_modules/eslint/messages/no-config-found.txt

@@ -0,0 +1,7 @@
+ESLint couldn't find a configuration file. To set up a configuration file for this project, please run:
+
+    eslint --init
+
+ESLint looked for configuration files in <%= directoryPath %> and its ancestors. If it found none, it then looked in your home directory.
+
+If you think you already have a configuration file or if you need more help, please stop by the ESLint chat room: https://gitter.im/eslint/eslint

node_modules/eslint/messages/plugin-missing.txt

@@ -0,0 +1,11 @@
+ESLint couldn't find the plugin "<%- pluginName %>".
+
+(The package "<%- pluginName %>" was not found when loaded as a Node module from the directory "<%- resolvePluginsRelativeTo %>".)
+
+It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
+
+    npm install <%- pluginName %>@latest --save-dev
+
+The plugin "<%- pluginName %>" was referenced from the config file in "<%- importerName %>".
+
+If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team.

node_modules/eslint/messages/print-config-with-directory-path.txt

@@ -0,0 +1,2 @@
+The '--print-config' CLI option requires a path to a source code file rather than a directory.
+See also: https://eslint.org/docs/user-guide/command-line-interface#--print-config

node_modules/eslint/messages/whitespace-found.txt

@@ -0,0 +1,3 @@
+ESLint couldn't find the plugin "<%- pluginName %>". because there is whitespace in the name. Please check your configuration and remove all whitespace from the plugin name.
+
+If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team.