[templates] Add yarn-error.log to .npmignore (expo#6024)

It turns out expo-template-blank and expo-template-blank-typescript got published to the npm registry with yarn-error.log included. This can be confusing, when trying to debug issues, since it looks like Yarn produced an error log, when in fact it was just extracted from the template by `expo init`. Adding yarn-error.log to .npmignore should prevent the file from being included in future releases.
lang-xin · Oct 18, 2019 · 33cff56 · 33cff56
1 parent 0e32331
commit 33cff56
Show file tree

Hide file tree

Showing 4 changed files with 24 additions and 0 deletions.
diff --git a/templates/expo-template-bare-minimum/.npmignore b/templates/expo-template-bare-minimum/.npmignore
@@ -0,0 +1,11 @@
+*.jks
+*.key
+*.mobileprovision
+*.p12
+*.p8
+.expo
+.npmignore
+.vscode
+package-lock.json
+yarn.lock
+yarn-error.log
diff --git a/templates/expo-template-bare-typescript/.npmignore b/templates/expo-template-bare-typescript/.npmignore
@@ -0,0 +1,11 @@
+*.jks
+*.key
+*.mobileprovision
+*.p12
+*.p8
+.expo
+.npmignore
+.vscode
+package-lock.json
+yarn.lock
+yarn-error.log
diff --git a/templates/expo-template-blank-typescript/.npmignore b/templates/expo-template-blank-typescript/.npmignore
@@ -8,3 +8,4 @@
 .vscode
 package-lock.json
 yarn.lock
+yarn-error.log
diff --git a/templates/expo-template-blank/.npmignore b/templates/expo-template-blank/.npmignore
@@ -8,3 +8,4 @@
 .vscode
 package-lock.json
 yarn.lock
+yarn-error.log