CODEWITHSUNDEEP
react-native
Arash
Arash

Reputation: 12465

react-native packager too long to start on windows

I have these numbers on packager time for my react-native project on a windows box

[7:56:23 PM] Crawling File System (104933ms)

[7:56:23 PM] Building in-memory fs for JavaScript

[7:56:30 PM] Building in-memory fs for JavaScript (7573ms)

[7:56:30 PM] Building in-memory fs for Assets

[7:56:39 PM] Building in-memory fs for Assets (8674ms)

[7:56:39 PM] Building Haste Map

[7:56:42 PM] Building (deprecated) Asset Map

[7:56:43 PM] Building (deprecated) Asset Map (1498ms)

[7:56:43 PM] Building Haste Map (4385ms)

[7:56:43 PM] Building Dependency Graph (125573ms)

[7:57:52 PM] request:/index.android.bundle?platform=android&dev=true&hot=false

[7:57:52 PM] find dependencies

[7:57:54 PM] find dependencies (1545ms)

[7:57:54 PM] transform

This doesn't look normal. Is there anythig I can do to make it run a bit faster.

BTW, my dependencies are 

"dependencies": {
    "firebase": "^2.4.1",
    "react-native": "^0.20.0",
    "react-native-simple-store": "^0.1.0",
    "react-redux": "^4.4.0",
    "redux": "^3.3.1",
    "redux-thunk": "^1.0.3"
  }

Upvotes: 1

Views: 820

Answers (2)

Eric Rozell
Eric Rozell

Reputation: 146

This can be normal for large projects. Depending on which version of node you're using, since you're probably not using watchman, the file watcher and dependency graph can take a long time to initialize.

Upvotes: 0

Chris Geirman
Chris Geirman

Reputation: 9684

Have you tried installing the gradle daemon?

Use gradle daemon

React Native Android use gradle as a build system. We recommend to enable gradle daemon functionality which may result in up to 50% improvement in incremental build times for changes in java code. Learn here how to enable it for your platform.

Upvotes: 0

Related Questions