Packager not handling .babelignore'd files due to sourcemap generation logic #13168

Activity

1. kevinold commented on Mar 27, 2017

   

   kevinold

   on Mar 27, 2017

   Author

   More actions

   @davidaurelio Hi David, see this issue. Adding you here as this might be related to your recent patch (0849f84#diff-4676ea0b3c55c65c3929aa993144f07f).
2. kevinold commented on Apr 25, 2017

   

   kevinold

   on Apr 25, 2017

   Author

   More actions

   @davidaurelio Any chance you could look into this?

   @loganfsmyth Would you be able to provide me with a bit of guidance on a patch for this issue if David is not able to?
3. kevinold commented on Apr 26, 2017

   

   kevinold

   on Apr 26, 2017

   Author

   More actions

   As a workaround I am using haul to package my app with my ignored files in .babelrc instead of a .babelignore like so:

   {
     "presets": ["react-native"],
     "ignore": [
       "my-ignored-lib.js"
     ]
   }
   

   👍React with 👍1Reacted by zakster12
4. kevinold

   added a commit that references this issue on Apr 27, 2017

   Properly handle babel ignored files, returning only the contents

   ...

   a6f8cb3
5. facebook-github-bot

   added 2 commits that reference this issue on May 6, 2017

   Properly handle babel ignored files, returning only the contents

   ...

   5905385

   Properly handle babel ignored files, returning only the contents

   ...

   7932b93
6. alexanderkjeldaas commented on May 25, 2017

   

   alexanderkjeldaas

   on May 25, 2017

   Last edited by alexanderkjeldaas

   More actions

   I'm having this issue, but with 0.45.0-rc.0, I'm getting out of memory. The behavior is not the same as with 0.40.0:

   transform[stdout]:
   transform[stdout]: <--- Last few GCs --->
   transform[stdout]:
   transform[stdout]: [24516:0x293f6c0]    67948 ms: Mark-sweep 1411.8 (1497.5) -> 1411.3 (1501.0) MB, 2285.6 / 0.0 ms  allocation failure GC in old space requested
   transform[stdout]: [24516:0x293f6c0]    70247 ms: Mark-sweep 1411.3 (1501.0) -> 1411.3 (1470.0) MB, 2298.1 / 0.0 ms  last resort
   transform[stdout]: [24516:0x293f6c0]    72527 ms: Mark-sweep 1411.3 (1470.0) -> 1411.3 (1470.0) MB, 2280.0 / 0.0 ms  last resort
   transform[stdout]:
   transform[stdout]:
   transform[stdout]: <--- JS stacktrace --->
   transform[stdout]:
   transform[stdout]: ==== JS stack trace =========================================
   transform[stdout]:
   transform[stdout]: Security context: 0xca215ea66a1 <JS Object>
   transform[stdout]:     2: parseExprOp [rn-code/node_modules/babylon/lib/index.js:~3416] [pc=0x4bbbf43ea8](this=0x684952922d9 <a Parser with map 0x2d43317b7999>,left=0x337d1acdc149 <a Node with map 0x2d43317c8351>,leftStartPos=1220248,leftStartLoc=0x337d1acdc0d9 <a Position with map 0x2d43317c56f9>,minPrec=-1,noIn=0x28c0c4c02311 <undefined>)
   transform[stdout]:     3: parseMaybeAssign [rn-...
   transform[stdout]:
   transform[stderr]: FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
   transform[stderr]:  1: node::Abort() [/usr/bin/nodejs]
   transform[stderr]:  2: 0x134e91c [/usr/bin/nodejs]
   transform[stderr]:  3:
   transform[stderr]: v8::Utils::ReportOOMFailure(char const*, bool) [/usr/bin/nodejs]
   transform[stderr]:  4:
   transform[stderr]: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/usr/bin/nodejs]
   transform[stderr]:  5: v8::internal::Factory::NewUninitializedFixedArray(int) [/usr/bin/nodejs]
   transform[stderr]:  6: 0xe1f0f5 [/usr/bin/nodejs]
   transform[stderr]:  7:
   transform[stderr]: v8::internal::Runtime_GrowArrayElements(int, v8::internal::Object**, v8::internal::Isolate*) [/usr/bin/nodejs]
   transform[stderr]:  8: 0x4bbb7843a7
   

   node v7.10.0
7. hramos commented on Jul 31, 2017

   

   hramos

   on Jul 31, 2017

   Contributor

   More actions

   Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!

   If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

   • Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
   • If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
   • Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

   If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.
8. hramos

   added

   Icebox

   on Jul 31, 2017
9. hramos

   closed this as completedon Jul 31, 2017
10. alexanderkjeldaas commented on Aug 2, 2017

    

    alexanderkjeldaas

    on Aug 2, 2017

    More actions

    I still have the same out-of-memory issue with 0.46.4
11. GarimaMathur07 commented on Jan 10, 2018

    

    GarimaMathur07

    on Jan 10, 2018

    More actions

    @alexanderkjeldaas did you find any solution for Android?
12. sujitpk-perennial commented on Jul 12, 2018

    

    sujitpk-perennial

    on Jul 12, 2018

    More actions

    @alexanderkjeldaas @GarimaMathur07 I am also getting JavaScript heap out of memory issue for large file. How you resolved this?
13. facebook-github-bot

    added a commit that references this issue on Jul 24, 2018

    React sync for revisions ae14317...ca0941f

    ...

    70913a4
14. react

    locked as resolved and limited conversation to collaborators on Jul 31, 2018
15. react-native-bot

    added

    Resolution: LockedThis issue was locked by the bot.This issue was locked by the bot.

    on Jul 31, 2018