Dependency on outdated version of glob #2454

Activity

1. ej612 commented on Mar 17, 2026

   

   ej612

   on Mar 17, 2026

   Author

   More actions

   Update: It's not a misconfiguration in our project, even when starting from scratch with:

   npm init
   npm i alasql
   

   I end up with glob 7.2.3. Here's the output of npm why glob:

   glob@7.2.3 optional peer
   node_modules/glob
     glob@"^7.1.1" from @react-native/codegen@0.82.1
     node_modules/@react-native/codegen
       @react-native/codegen@"0.82.1" from react-native@0.82.1
       node_modules/react-native
         peer react-native@"*" from @react-native/virtualized-lists@0.82.1
         node_modules/@react-native/virtualized-lists
           @react-native/virtualized-lists@"0.82.1" from react-native@0.82.1
         peer react-native@"*" from react-native-fs@2.20.0
         node_modules/react-native-fs
           optional react-native-fs@"^2.20.0" from alasql@4.17.0
           node_modules/alasql
             alasql@"^4.17.0" from the root project
     glob@"^7.1.1" from react-native@0.82.1
     node_modules/react-native
       peer react-native@"*" from @react-native/virtualized-lists@0.82.1
       node_modules/@react-native/virtualized-lists
         @react-native/virtualized-lists@"0.82.1" from react-native@0.82.1
       peer react-native@"*" from react-native-fs@2.20.0
       node_modules/react-native-fs
         optional react-native-fs@"^2.20.0" from alasql@4.17.0
         node_modules/alasql
           alasql@"^4.17.0" from the root project
     glob@"^7.1.3" from rimraf@3.0.2
     node_modules/rimraf
       rimraf@"^3.0.2" from chromium-edge-launcher@0.2.0
       node_modules/chromium-edge-launcher
         chromium-edge-launcher@"^0.2.0" from @react-native/dev-middleware@0.82.1
         node_modules/@react-native/dev-middleware
           @react-native/dev-middleware@"0.82.1" from @react-native/community-cli-plugin@0.82.1
           node_modules/@react-native/community-cli-plugin
             @react-native/community-cli-plugin@"0.82.1" from react-native@0.82.1
             node_modules/react-native
               peer react-native@"*" from @react-native/virtualized-lists@0.82.1
               node_modules/@react-native/virtualized-lists
                 @react-native/virtualized-lists@"0.82.1" from react-native@0.82.1
               peer react-native@"*" from react-native-fs@2.20.0
               node_modules/react-native-fs
                 optional react-native-fs@"^2.20.0" from alasql@4.17.0
                 node_modules/alasql
                   alasql@"^4.17.0" from the root project
     glob@"^7.1.4" from test-exclude@6.0.0
     node_modules/test-exclude
       test-exclude@"^6.0.0" from babel-plugin-istanbul@6.1.1
       node_modules/babel-plugin-istanbul
         babel-plugin-istanbul@"^6.1.1" from @jest/transform@29.7.0
         node_modules/@jest/transform
           @jest/transform@"^29.7.0" from babel-jest@29.7.0
           node_modules/babel-jest
             babel-jest@"^29.7.0" from react-native@0.82.1
             node_modules/react-native
               peer react-native@"*" from @react-native/virtualized-lists@0.82.1
               node_modules/@react-native/virtualized-lists
                 @react-native/virtualized-lists@"0.82.1" from react-native@0.82.1
               peer react-native@"*" from react-native-fs@2.20.0
               node_modules/react-native-fs
                 optional react-native-fs@"^2.20.0" from alasql@4.17.0
                 node_modules/alasql
                   alasql@"^4.17.0" from the root project
         babel-plugin-istanbul@"^6.1.1" from babel-jest@29.7.0
         node_modules/babel-jest
           babel-jest@"^29.7.0" from react-native@0.82.1
           node_modules/react-native
             peer react-native@"*" from @react-native/virtualized-lists@0.82.1
             node_modules/@react-native/virtualized-lists
               @react-native/virtualized-lists@"0.82.1" from react-native@0.82.1
             peer react-native@"*" from react-native-fs@2.20.0
             node_modules/react-native-fs
               optional react-native-fs@"^2.20.0" from alasql@4.17.0
               node_modules/alasql
                 alasql@"^4.17.0" from the root project
   
2. ej612 commented on Mar 18, 2026

   

   ej612

   on Mar 18, 2026

   Author

   More actions

   It looks like it's react-native-fs that's pulling in that dependency. The last release was 4 years ago, I have found this post by someone maintaining a fork. @mathiasrw, would it be worth it to look into migrating?
3. ej612 commented on Mar 24, 2026

   

   ej612

   on Mar 24, 2026

   Last edited by ej612

   Author

   More actions

   Since react-native-fs is declared as optional, a fix for this problem could also be to declare it under peerDependenciesMeta instead of optionalDependencies.
   This would be a breaking change, as the package would no longer be automatically installed, but it would be easily fixable and would not require looking into a replacement package.

   Without knowing anything about the reasoning behind the inclusion of react-native-fs, my understanding after having a look at the code is that what we want to do:

   If react-native-fs is available in target env, use it. If it isn't, do nothing.

   This, however, means that the dependency really should be declared as a peer, as we don't want to add any runtime dependencies. Is this understanding correct?
4. ej612

   added a commit that references this issue on Mar 29, 2026

   Make `react-native-fs` an optional peer dependency

   ...

   This issue will close once commit 2435b91 is merged into the 'develop' branch.

   2435b91
5. mathiasrw commented on Apr 1, 2026

   

   mathiasrw

   on Apr 1, 2026

   Member

   More actions

   Is this understanding correct?

   yes, this understanding is correct. The decision is from a different time - a echo of a different programming era. We are moving it to peer dependency for sure next time we bump the major version.

   For now I will bump the glob dep.

   👍React with 👍1Reacted by ej612
6. mathiasrw commented on Apr 1, 2026

   

   mathiasrw

   on Apr 1, 2026

   Member

   More actions

   Fix released as part of v4.17.1
7. mathiasrw

   closed this as completedon Apr 1, 2026
8. ej612 commented on Apr 1, 2026

   

   ej612

   on Apr 1, 2026

   Author

   More actions

   Hi there, thank you! I tested 4.17.1 and the problem persists, which makes sense. Can we keep this issue open until the next major?