issues
search
jpudysz
/
react-native-is-maestro
Detect synchronously if your app is currently running in an E2E test environment with Maestro
MIT License
36
stars
5
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
fix: change port to work with maestro >= 1.37.0
#17
joepatosh
opened
1 month ago
1
Add Maestro 1.37.x support
#16
JampaUchoa
opened
3 months ago
1
feat: upgrade deps, fix issue with monorepo builds on web
#15
jpudysz
closed
5 months ago
0
feat: make asynchronous
#14
niall-shaw
closed
5 months ago
2
Invariant Violation: Calling synchronous methods on native modules is not supported in Chrome.
#13
niall-shaw
closed
5 months ago
10
feat: add support for RN 0.72
#12
jpudysz
closed
1 year ago
0
Add react-native 0.70.x support
#11
retyui
closed
1 year ago
4
Make an instalation more clear
#10
retyui
closed
1 year ago
1
pod install fail RN-is-maestro@1.2.2 and RN#0.70.x
#9
retyui
closed
1 year ago
3
Unlock nodejs
#8
ghost
closed
1 year ago
0
Library is detecting a different iOS port to what's recommended
#7
matt-dalton
closed
1 year ago
1
feat: readme and 2.0 version
#6
jpudysz
closed
1 year ago
0
feat: support new maestro cli
#5
jpudysz
closed
1 year ago
0
fix: change port number to adapt new version
#4
amanjeetsingh150
closed
1 year ago
3
Executing maestro test command doesn't detect maestro
#3
amanjeetsingh150
closed
1 year ago
2
chore: update kotlin code
#2
jpudysz
closed
1 year ago
0
refactor(android): move implementation inside module
#1
atlj
closed
1 year ago
0