Expo fails to start the project: error Invalid regular expression: /(.*\\fixtures #1074

4erem6a · 2019-10-05T22:27:35Z

Description

I just initialize a new expo project and try to start it, but every time I get this error. This also happens with all my expo projects on this machine.

Expected Behavior

I use yarn start and expect expo to start the project.

Observed Behavior

PS E:\Projects\test> $env:expo_debug = 'true'
PS E:\Projects\test> yarn start
yarn run v1.19.0
$ expo start
Starting project at E:\Projects\test
Expo DevTools is running at http://localhost:19002
Opening DevTools in the browser... (press shift-d to disable)
error Invalid regular expression: /(.*\\__fixtures__\\.*|node_modules[\\\]react[\\\]dist[\\\].*|website\\node_modules\\.*|heapCapture\\bundle\.js|.*\\__tests__\\.*)$/: Unterminated character class. Run CLI with --verbose flag for more details.

Metro Bundler process exited with code 1
Error: Metro Bundler process exited with code 1
    at ChildProcess.<anonymous> (C:\@expo\xdl@56.2.7\src\Project.ts:1804:16)
    at Object.onceWrapper (events.js:300:26)
    at ChildProcess.emit (events.js:210:5)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Environment

  Expo CLI 3.2.3 environment info:
    System:
      OS: Windows 10
    Binaries:
      Yarn: 1.19.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
      npm: 6.11.3 - C:\Program Files\nodejs\npm.CMD
    IDEs:
      Android Studio: Version  3.4.0.0 AI-183.6156.11.34.5522156

The text was updated successfully, but these errors were encountered:

ghost · 2019-10-07T09:06:42Z

same here

ghost · 2019-10-07T09:14:37Z

Fixed it by downgrading Node version

IanSaucy · 2019-10-09T04:59:56Z

@yuraheiko From what version and to what version of node did you downgrade?

painkkiller · 2019-10-09T11:57:16Z

same here

ghost · 2019-10-09T11:59:46Z

@yuraheiko From what version and to what version of node did you downgrade?

I dont remember which version I had, but for me works node 10 LTS.

GollyJer · 2019-10-12T01:28:54Z

Just updated to Node 12.12.0 and got this error. ☹
(Using Windows 10)

GollyJer · 2019-10-12T04:32:16Z

Tried
12.11 👎
12.10 👎
12.9 👍 ✔

Using expo-cli 3.3.0.

kundankumarr · 2019-10-12T13:17:26Z

i just start react native using expo cli .. and get this error and im confused..
error Invalid regular expression: /(.\fixtures\.|node_modules[\]react[\]dist[\].|website\node_modules\.|heapCapture\bundle.js|.\tests\.)$/: Unterminated character class. Run CLI with --verbose flag for more details.

Metro Bundler process exited with code 1
Set EXPO_DEBUG=true in your env to view the stack trace.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ start: expo start
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\user\AppData\Roaming\npm-cache_logs\2019-10-12T13_00_57_090Z-debug.log

frazermg · 2019-10-13T01:15:56Z

I had this error too, downgraded to 10.16.3 and it's working.

ocharlespereira · 2019-10-13T17:14:04Z

Qual o comando que vcs usam para voltar versão sem dar erro?

usei o comando cinst nodejs.install --force -version 12.9 -allow-downgrade e não obtive sucesso, está dando erro

Failures

-allow-downgrade - -allow-downgrade not installed. The package was not found with the source(s) listed.
Source(s): 'https://chocolatey.org/api/v2/'
NOTE: When you specify explicit sources, it overrides default sources.
If the package version is a prerelease and you didn't specify --pre,
the package may not be found.
Please see https://chocolatey.org/docs/troubleshooting for more
assistance.
-version - -version not installed. The package was not found with the source(s) listed.
Source(s): 'https://chocolatey.org/api/v2/'
NOTE: When you specify explicit sources, it overrides default sources.
If the package version is a prerelease and you didn't specify --pre,
the package may not be found.
Please see https://chocolatey.org/docs/troubleshooting for more
assistance.
12.9 - 12.9 not installed. The package was not found with the source(s) listed.
Source(s): 'https://chocolatey.org/api/v2/'
NOTE: When you specify explicit sources, it overrides default sources.
If the package version is a prerelease and you didn't specify --pre,
the package may not be found.
Please see https://chocolatey.org/docs/troubleshooting for more
assistance.

ocharlespereira · 2019-10-13T17:15:48Z

What command do you use to get back to the version without error?

cinst nodejs.install --force -version 12.9 -allow-downgrade and unsuccessful, is giving error...

lanort · 2019-10-15T06:14:12Z

I had the node v12.12.0 (just recently via choco install nodejs) installed and got the following error:

C:\Users\alexa\jj>expo start
Starting project at C:\Users\alexa\jj
Expo DevTools is running at http://localhost:19002
Opening DevTools in the browser... (press shift-d to disable)
error Invalid regular expression: /(.\fixtures\.|node_modules[\]react[\]dist[\].|website\node_modules\.|heapCapture\bundle.js|.\tests\.)$/: Unterminated character class. Run CLI with --verbose flag for more details.

Metro Bundler process exited with code 1
Set EXPO_DEBUG=true in your env to view the stack trace.

This downgrade fixed that:

choco uninstall nodejs
choco install nodejs --version=12.9.1

Aleladeia99 · 2019-10-16T19:37:22Z

how can I uninstall nodejs with npm?

umairbabar1995 · 2019-10-20T18:14:37Z

Just updated to Node 12.12.0 and got this error. ☹
(Using Windows 10)
removed Node 12.12.0 and install Node 10 LTS now its working

bgohsman · 2019-10-23T21:59:18Z

Thank you! I had everything working on my MacBook Pro and my Windows 10 laptop but could not, for the life of me, get things working on my desktop Windows 10 machine. Sure enough, choco installed the LTS version, which was 12.12.0 by that time. Uninstalled it and went back to the newest 10.x and everyone is happy again.

hadessama1994 · 2019-10-25T01:54:08Z

Got this issue today on windows, but don't need to downgrade node, just as discussed on stackoverflow just need to change some hashes on your project:

\node_modules\metro-config\src\defaults\blacklist.js

var sharedBlacklist = [
  /node_modules[/\\]react[/\\]dist[/\\].*/,
  /website\/node_modules\/.*/,
  /heapCapture\/bundle\.js/,
  /.*\/__tests__\/.*/
];

change to:

var sharedBlacklist = [
  /node_modules[\/\\]react[\/\\]dist[\/\\].*/,
  /website\/node_modules\/.*/,
  /heapCapture\/bundle\.js/,
  /.*\/__tests__\/.*/
];

Hope it works like worked for me :)

tkud04 · 2019-10-26T13:14:34Z

Thank you @hadessama1994! Changing the value of the sharedBlackList variable in metro config src worked for me on windows 10. Just downloaded node 12.13.0 and did not have to downgrade.

djsing · 2019-10-27T12:26:51Z

@hadessama1994 This worked for me too. To think a single character escape is the issue xD.

JJader · 2019-10-27T20:58:32Z

@hadessama1994 Muito obrigado companheiro !!

ahmostafa91 · 2019-10-28T05:33:25Z

Got this issue today on windows, but don't need to downgrade node, just as discussed on stackoverflow just need to change some hashes on your project:

\node_modules\metro-config\src\defaults\blacklist.js
var sharedBlacklist = [
  /node_modules[/\\]react[/\\]dist[/\\].*/,
  /website\/node_modules\/.*/,
  /heapCapture\/bundle\.js/,
  /.*\/__tests__\/.*/
];
change to:
var sharedBlacklist = [
  /node_modules[\/\\]react[\/\\]dist[\/\\].*/,
  /website\/node_modules\/.*/,
  /heapCapture\/bundle\.js/,
  /.*\/__tests__\/.*/
];
Hope it works like worked for me :)

Thank's a lot , it works for me

osix · 2019-10-28T20:05:08Z

Got this issue today on windows, but don't need to downgrade node, just as discussed on stackoverflow just need to change some hashes on your project:

\node_modules\metro-config\src\defaults\blacklist.js
var sharedBlacklist = [
  /node_modules[/\\]react[/\\]dist[/\\].*/,
  /website\/node_modules\/.*/,
  /heapCapture\/bundle\.js/,
  /.*\/__tests__\/.*/
];
change to:
var sharedBlacklist = [
  /node_modules[\/\\]react[\/\\]dist[\/\\].*/,
  /website\/node_modules\/.*/,
  /heapCapture\/bundle\.js/,
  /.*\/__tests__\/.*/
];
Hope it works like worked for me :)

It's more a crutch rather than a good solution. It will work until the metro-config is updated.
I have the same issue and I've downgraded to the node version 12.9.1. Only that really helped. Thanks to @GollyJer

Summary: **Summary** On Windows with Node.js v12.x.x, Metro crashes with ``` SyntaxError: Invalid regular expression: /(.*\\__fixtures__\\.*|node_modules[\\\]react[\\\]dist[\\\].*|website\\node_modules\\.*|heapCapture\\bundle\.js|.*\\__tests__\\.*)$/: Unterminated character class ``` This has been reported in #453, facebook/react-native#26829, facebook/react-native#26969, facebook/react-native#26878, facebook/react-native#26598, expo/expo-cli#1147 and expo/expo-cli#1074. There are a few open pull requests attempting to fix this same issue: * #464 * #461 * #458 * #454 However, none of the existing PRs address the *root cause* of this error: the `escapeRegExp` function in `blacklist.js` tries to convert regular expressions to be agnostic to the path separator ("/" or "\\"), but turns some valid regular expressions to invalid syntax. The error was is this line: https://github.com/facebook/metro/blob/142348f5345e40ce2075fc7f9dfa30c5d31fee2a/packages/metro-config/src/defaults/blacklist.js#L28 When given a regular expression, such as `/node_modules[/\\]react[/\\]dist[/\\].*/`, on Windows where `path.sep` is `\` (which is also an escape character in regular expressions), this gets turned into `/node_modules[\\\]react[\\\]dist[\\\].*/`, resulting in the `Unterminated character class` error. Automatically replacing `[/]` with `[\]` is an error, as is replacing `[\/]` with `[\\]`, because in both of these cases the backslash before the end of character class "]" escapes it, and the character class becomes unterminated. Therefore, this PR changes the code to look for both escaped forward slash `\/` and forward slash `/`, and always replace them with the escaped version (`\/` or `\\`, depending on the platform). This fixes #453. **Test plan** Added a test case that exercises the code with both `\` and `/` as path separators. Pull Request resolved: #468 Differential Revision: D18201730 Pulled By: cpojer fbshipit-source-id: 6bb694178314c39d4d6a0fd9f8547bfa2c36f894

dharmveer97 · 2019-11-02T07:31:27Z

error Invalid regular expression: /(.\fixtures\.|node_modules[\]react[\]dist[\].|website\node_modules\.|heapCapture\bundle.js|.\tests\.)$/: Unterminated character class. Run CLI with --verbose flag for more details.

Metro Bundler process exited with code 1

realka · 2019-11-02T19:48:45Z

Got this issue today on windows, but don't need to downgrade node, just as discussed on stackoverflow just need to change some hashes on your project:

\node_modules\metro-config\src\defaults\blacklist.js
var sharedBlacklist = [
  /node_modules[/\\]react[/\\]dist[/\\].*/,
  /website\/node_modules\/.*/,
  /heapCapture\/bundle\.js/,
  /.*\/__tests__\/.*/
];
change to:
var sharedBlacklist = [
  /node_modules[\/\\]react[\/\\]dist[\/\\].*/,
  /website\/node_modules\/.*/,
  /heapCapture\/bundle\.js/,
  /.*\/__tests__\/.*/
];
Hope it works like worked for me :)

Thanks worked! :)

sece15 · 2019-11-03T09:01:37Z

#1074 (comment)
muchas gracias funciona perfectamente

bonur · 2019-11-04T14:08:29Z

error Invalid regular expression: /(.*fixtures*.|node_modules[]react[]dist[].|website\node_modules.|heapCapture\bundle.js|.*tests*.)$/: Unterminated character class. Run CLI with --verbose flag for more details.

Metro Bundler process exited with code 1

Same for me. I did 'fix' blacklist.js

emiliano249 · 2019-11-04T21:25:01Z

#1074 (comment)

It Works for me on Windows 7 Ultimate. Thank You!!!

rustyonrampage · 2019-11-08T07:00:56Z

Got this issue today on windows, but don't need to downgrade node, just as discussed on stackoverflow just need to change some hashes on your project:

\node_modules\metro-config\src\defaults\blacklist.js
var sharedBlacklist = [
  /node_modules[/\\]react[/\\]dist[/\\].*/,
  /website\/node_modules\/.*/,
  /heapCapture\/bundle\.js/,
  /.*\/__tests__\/.*/
];
change to:
var sharedBlacklist = [
  /node_modules[\/\\]react[\/\\]dist[\/\\].*/,
  /website\/node_modules\/.*/,
  /heapCapture\/bundle\.js/,
  /.*\/__tests__\/.*/
];
Hope it works like worked for me :)

It works. But everytime I add a new package, it has to be done again. Annoying...

deadmann · 2019-11-09T10:09:13Z

Got this issue today on windows, but don't need to downgrade node, just as discussed on stackoverflow just need to change some hashes on your project:

\node_modules\metro-config\src\defaults\blacklist.js
var sharedBlacklist = [
  /node_modules[/\\]react[/\\]dist[/\\].*/,
  /website\/node_modules\/.*/,
  /heapCapture\/bundle\.js/,
  /.*\/__tests__\/.*/
];
change to:
var sharedBlacklist = [
  /node_modules[\/\\]react[\/\\]dist[\/\\].*/,
  /website\/node_modules\/.*/,
  /heapCapture\/bundle\.js/,
  /.*\/__tests__\/.*/
];
Hope it works like worked for me :)
It works. But everytime I add a new package, it has to be done again. Annoying...

Not For me:

E:\Hassan\ReactTutorial\rn-first-app>npm start

@ start E:\Hassan\ReactTutorial\rn-first-app
expo start

\Starting project at E:\Hassan\ReactTutorial\rn-first-app
Expo DevTools is running at http://localhost:19002
Opening DevTools in the browser... (press shift-d to disable)
error Unexpected token 'function'. Run CLI with --verbose flag for more details.

Metro Bundler process exited with code 1
Set EXPO_DEBUG=true in your env to view the stack trace.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ start: expo start
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Hassan\AppData\Roaming\npm-cache_logs\2019-11-09T10_08_29_028Z-debug.log

E:\Hassan\ReactTutorial\rn-first-app>

fson · 2019-11-13T20:29:06Z

The underlying Metro issue has been fixed upstream in facebook/metro@7c6f30b.

dotjsNet · 2019-11-17T17:03:32Z

Install Nodejs node-v10.15.3 it should resolve the issue.

mmarcwabo · 2019-11-18T09:56:45Z

Had the same problem (with nodejs 12.13.0).
My problem has been solved by both unistalling the 12.13 version and downgrade it to 12.9

tim92109 · 2019-11-18T22:34:52Z

Another confirmation that the fix to blacklist.js worked. I CRINGE every time I'm prompted to update expo-cli. Unlike every other package I use, it's never simple and/or flawless.

brentvatne · 2019-11-18T22:38:12Z

@tim92109 - in this case the error that you appear to be encountering is not actually from expo-cli but from tools that underly it: node and metro (the react-native packager). as you can see from this stackoverflow post this error happens on any react-native project. further, the maintainer of expo-cli (@fson) actually went and fixed the bug in metro itself (facebook/metro@7c6f30b), which he does not maintain. so i don't think it's really fair to blame expo-cli here.

nzrubin · 2019-11-21T02:38:30Z

Have the latest node JS 13.1.0 but same error
Great Thanks!
adjusting as advised above
\node_modules\metro-config\src\defaults\blacklist.js
worked for me
W10 Node 13.1.0

emiliano249 · 2019-11-21T12:28:38Z

Thanks I was about to go crazy;) El mié., 20 nov. 2019 a las 23:38, nzrubin (<notifications@github.com>) escribió:

…

Great Thanks! adjusting as advised above \node_modules\metro-config\src\defaults\blacklist.js worked for me W10 Node 13.1.0 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1074?email_source=notifications&email_token=AL72SHK2MRDVZB6REC6472DQUXYCRA5CNFSM4I5ZR67KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEYRX2Q#issuecomment-556866538>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AL72SHI3CBWXZ7B74WSKHTTQUXYCRANCNFSM4I5ZR67A> .

lucaslucenagithub · 2019-11-24T02:00:58Z

Got this issue today on windows, but don't need to downgrade node, just as discussed on stackoverflow just need to change some hashes on your project:

\node_modules\metro-config\src\defaults\blacklist.js
var sharedBlacklist = [
  /node_modules[/\\]react[/\\]dist[/\\].*/,
  /website\/node_modules\/.*/,
  /heapCapture\/bundle\.js/,
  /.*\/__tests__\/.*/
];
change to:
var sharedBlacklist = [
  /node_modules[\/\\]react[\/\\]dist[\/\\].*/,
  /website\/node_modules\/.*/,
  /heapCapture\/bundle\.js/,
  /.*\/__tests__\/.*/
];
Hope it works like worked for me :)

finally i could did this thanks to you!

RealDyllon · 2019-11-24T04:50:20Z

@lucasgit2000 's solution worked for me. Thanks mate.

Edit: running nodejs v12.13.1 (I didn’t downgrade)

sugeng-sulistiyawan · 2019-11-24T10:05:10Z

Tried
12.11 👎
12.10 👎
12.9 👍 ✔

Using expo-cli 3.3.0.

Worked for me!!

rahul12330 · 2019-11-24T11:23:48Z

i just start react native using expo cli .. and get this error and im confused..
error Invalid regular expression: /(.*fixtures*.|node_modules[]react[]dist[].|website\node_modules.|heapCapture\bundle.js|.*tests*.)$/: Unterminated character class. Run CLI with --verbose flag for more details.

Metro Bundler process exited with code 1
Set EXPO_DEBUG=true in your env to view the stack trace.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ start: expo start
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\user\AppData\Roaming\npm-cache_logs\2019-10-12T13_00_57_090Z-debug.log

How did you solve this?

RealDyllon · 2019-11-24T11:32:04Z

@rahul12330 instructions here: #1074 (comment)

mridul037 · 2019-11-26T03:31:58Z

https://stackoverflow.com/questions/58120990/how-to-resolve-the-error-on-react-native-start/58199866#58199866

see this stack overflow discussion
you just have to change \node_modules\metro-config\src\defaults\blacklist.js .

var sharedBlacklist = [
  /node_modules[/\\]react[/\\]dist[/\\].*/,
  /website\/node_modules\/.*/,
  /heapCapture\/bundle\.js/,
  /.*\/__tests__\/.*/
];

this to

var sharedBlacklist = [
  /node_modules[\/\\]react[\/\\]dist[\/\\].*/,
  /website\/node_modules\/.*/,
  /heapCapture\/bundle\.js/,
  /.*\/__tests__\/.*/
];

Note:: each time you do npm install do update the file

tim92109 · 2019-11-26T17:14:01Z

Real bummer about Expo which is the only reason I sometimes don't like developing in React. Last 5 expo updates caused issues including this one. HATE it when I see a new version of Expo is available. Wish they would at least test new versions before pushing them.

KHARCHO · 2019-11-26T18:42:42Z

Must downgrade to 12.9.1 version of Node.js ... I think that is the latest version that works without crashing... here is the download link:

https://nodejs.org/download/release/v12.9.1/

tarunjuneja · 2019-11-27T06:12:47Z

after node downgrade i further did

npm uninstall --g expo-cli
npm install --g expo-cli

to be able to compile my code

I did not make change into any local node module. Everything worked.

prititripathi · 2019-11-27T08:23:39Z

@hadessama1994 thank you so much :)
Saved my day.

deadmann · 2019-11-27T09:14:38Z

Real bummer about Expo which is the only reason I sometimes don't like developing in React. Last 5 expo updates caused issues including this one. HATE it when I see a new version of Expo is available. Wish they would at least test new versions before pushing them.

that why from my child hood i believed in Microsoft, you hardly found a functionally that get remove and cause old code to crash, you still can run and use codes from hundred of years ago :-"
Yet since new manager open the door to Open Source developer,... i'm losing my believes in them too... but codes should be solid, we should add, not remove, we may only flag obsolete functionality, but not change or remove them,... just add to system in a way that doesn't target the old codes.

RealDyllon · 2019-11-27T14:07:52Z

Real bummer about Expo which is the only reason I sometimes don't like developing in React. Last 5 expo updates caused issues including this one. HATE it when I see a new version of Expo is available. Wish they would at least test new versions before pushing them.

that why from my child hood i believed in Microsoft, you hardly found a functionally that get remove and cause old code to crash, you still can run and use codes from hundred of years ago :-"
Yet since new manager open the door to Open Source developer,... i'm losing my believes in them too... but codes should be solid, we should add, not remove, we may only flag obsolete functionality, but not change or remove them,... just add to system in a way that doesn't target the old codes.

Have you even used Windows 10?

soletan · 2019-11-27T16:16:58Z

@fson It's a pity no one's picking up your real solution here but adding more noise to the comments. Any chance to get your fix without requiring someone updating this repo's dependencies first?

brentvatne · 2019-11-27T19:23:48Z

👋 if you came here from the expo-cli warning.

the recommended solution is to do the following:

delete node_modules
delete your lockfiles (npm-lock.json or yarn.lock)
run npm install or yarn again.

the important thing is that when you install your dependencies you end up with metro@0.56.4 or greater in your lockfile!

does this now work for you for some reason? other temporary solutions if you encounter this error are:

option 1. downgrade to node 12.9
option 2. follow these instructions to patch node_modules: https://stackoverflow.com/a/58199866/659988

if you are curious why you are seeing this error, it is because a specific version of a package called metro-config (a package used by react-native) has some code that is incompatible with certain versions of node 12.

fson mentioned this issue Oct 28, 2019

Fix blacklist regex syntax errors facebook/metro#468

Closed

fson changed the title ~~Expo fails to start the project~~ Expo fails to start the project: error Invalid regular expression: /(.*\\__fixtures__ Nov 13, 2019

fson mentioned this issue Nov 14, 2019

Expo Start error after uninstall/install of expo-cli and nodejs #1147

Closed

brentvatne mentioned this issue Nov 27, 2019

i have this error message when running expo. plz help me fix this #1274

Closed

expo locked as off-topic and limited conversation to collaborators Nov 27, 2019

brentvatne self-assigned this Nov 27, 2019

brentvatne closed this as completed in 276648c Jan 6, 2020

carlosloureda referenced this issue in udacity/reactnd-UdaciFitness-complete Feb 1, 2020

Changes for History-calendar

57d2493

Expo fails to start the project: error Invalid regular expression: /(.*\\__fixtures__ #1074

Expo fails to start the project: error Invalid regular expression: /(.*\\__fixtures__ #1074

Comments

4erem6a commented Oct 5, 2019

Description

Expected Behavior

Observed Behavior

Environment

ghost commented Oct 7, 2019

ghost commented Oct 7, 2019

IanSaucy commented Oct 9, 2019

painkkiller commented Oct 9, 2019

ghost commented Oct 9, 2019

GollyJer commented Oct 12, 2019 • edited Loading

GollyJer commented Oct 12, 2019 • edited Loading

kundankumarr commented Oct 12, 2019

frazermg commented Oct 13, 2019

ocharlespereira commented Oct 13, 2019

ocharlespereira commented Oct 13, 2019 • edited Loading

lanort commented Oct 15, 2019

Aleladeia99 commented Oct 16, 2019

umairbabar1995 commented Oct 20, 2019 • edited Loading

bgohsman commented Oct 23, 2019

hadessama1994 commented Oct 25, 2019

tkud04 commented Oct 26, 2019

djsing commented Oct 27, 2019

JJader commented Oct 27, 2019

ahmostafa91 commented Oct 28, 2019

osix commented Oct 28, 2019

dharmveer97 commented Nov 2, 2019

realka commented Nov 2, 2019

sece15 commented Nov 3, 2019

bonur commented Nov 4, 2019

emiliano249 commented Nov 4, 2019

rustyonrampage commented Nov 8, 2019

deadmann commented Nov 9, 2019

fson commented Nov 13, 2019

dotjsNet commented Nov 17, 2019

mmarcwabo commented Nov 18, 2019

tim92109 commented Nov 18, 2019

brentvatne commented Nov 18, 2019 • edited Loading

nzrubin commented Nov 21, 2019 • edited Loading

emiliano249 commented Nov 21, 2019 via email

lucaslucenagithub commented Nov 24, 2019

RealDyllon commented Nov 24, 2019 • edited Loading

sugeng-sulistiyawan commented Nov 24, 2019

rahul12330 commented Nov 24, 2019

RealDyllon commented Nov 24, 2019

mridul037 commented Nov 26, 2019

tim92109 commented Nov 26, 2019

KHARCHO commented Nov 26, 2019 • edited Loading

tarunjuneja commented Nov 27, 2019 • edited Loading

prititripathi commented Nov 27, 2019

deadmann commented Nov 27, 2019

RealDyllon commented Nov 27, 2019

soletan commented Nov 27, 2019

brentvatne commented Nov 27, 2019 • edited Loading

Expo fails to start the project: error Invalid regular expression: /(.*\\fixtures #1074

Expo fails to start the project: error Invalid regular expression: /(.*\\fixtures #1074

GollyJer commented Oct 12, 2019 •

edited

Loading

GollyJer commented Oct 12, 2019 •

edited

Loading

ocharlespereira commented Oct 13, 2019 •

edited

Loading

umairbabar1995 commented Oct 20, 2019 •

edited

Loading

brentvatne commented Nov 18, 2019 •

edited

Loading

nzrubin commented Nov 21, 2019 •

edited

Loading

RealDyllon commented Nov 24, 2019 •

edited

Loading

KHARCHO commented Nov 26, 2019 •

edited

Loading

tarunjuneja commented Nov 27, 2019 •

edited

Loading

brentvatne commented Nov 27, 2019 •

edited

Loading