Comments (38)
After pinning to 16.4.6 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
from flagship.
Version 16.4.14 just got published.
Your tests are passing again with this version. Explicitly upgrade to this version 🚀
from flagship.
- The
devDependency
@types/react was updated from16.4.14
to16.4.15
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.4.15
to16.4.16
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.4.16
to16.4.17
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.4.17
to16.4.18
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.4.18
to16.7.0
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.7.0
to16.7.1
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.7.1
to16.7.2
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.7.2
to16.7.3
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.7.3
to16.7.4
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.7.4
to16.7.5
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.7.5
to16.7.6
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.7.6
to16.7.7
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.7.7
to16.7.8
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.7.8
to16.7.9
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.7.9
to16.7.10
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.7.10
to16.7.11
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.7.11
to16.7.12
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.7.12
to16.7.13
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.7.13
to16.7.14
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.7.14
to16.7.15
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.7.15
to16.7.16
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.7.16
to16.7.17
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.7.18
to16.7.19
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.7.19
to16.7.20
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.8.1
to16.8.2
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.8.2
to16.8.3
.
Your tests are still failing with this version. Compare changes
from flagship.
Keeping this. React is being updated manually but this is good reference for @types/react
from flagship.
- The
devDependency
@types/react was updated from16.8.3
to16.8.4
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.8.4
to16.8.5
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.8.5
to16.8.6
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.8.6
to16.8.7
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.8.7
to16.8.8
.
Your tests are still failing with this version. Compare changes
from flagship.
- The
devDependency
@types/react was updated from16.8.9
to16.8.10
.
Your tests are passing again with this update. Explicitly upgrade to this version 🚀
from flagship.
- The
devDependency
@types/react was updated from16.8.9
to16.8.10
.
Your tests are passing again with this update. Explicitly upgrade to this version 🚀
from flagship.
- The
devDependency
@types/react was updated from16.8.10
to16.8.11
.
Your tests are passing again with this update. Explicitly upgrade to this version 🚀
from flagship.
updating manually.
from flagship.
Related Issues (20)
- Dependabot needs permission to see react-native-restart
- Dependabot needs permission to see react-native-restart
- Dependabot needs permission to see react-native-restart
- Flatlists missing keyExtractors
- Custom Select component for web
- Cannot init on case sensitive file systems
- fscomponents: NestingButtons - Cannot close modal when button is pressed
- Dependabot can't parse your package-lock.json
- Dependabot can't parse your package-lock.json
- Dependabot can't parse your package-lock.json
- FSApp Router popTo HOT 2
- Android modifications are always returning the default values
- ModalHalfScreen component could have custom styles
- Broken link in create flagship app wiki page
- [Bug Report] Missing Recommended Icons
- [Bug Report] iOS Deployment Target Desync
- [Feature Report] Extend iOS keys Script HOT 1
- Issue with boxes HOT 3
- [Bug Report] Pin activesupport gem HOT 1
- [Feature Report] Move Code Signing to Ruby / Fastlane HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from flagship.