dependabot[bot] 848158d9a0 Bump com.vanniktech:gradle-maven-publish-plugin from 0.22.0 to 0.24.0 (#4511)
Summary:
Bumps [com.vanniktech:gradle-maven-publish-plugin](https://github.com/vanniktech/gradle-maven-publish-plugin) from 0.22.0 to 0.24.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/vanniktech/gradle-maven-publish-plugin/releases">com.vanniktech:gradle-maven-publish-plugin's releases</a>.</em></p>
<blockquote>
<h2>0.24.0</h2>
<ul>
<li>Support arbitrary Sonatype hosts instead of just oss.sonatype.org and s01.oss.sonatype.org.</li>
<li>Support adjusting timeouts for Sonatype related requests and operations. <a href="https://vanniktech.github.io/gradle-maven-publish-plugin/central/#timeouts">See docs</a></li>
<li>Internal change on how the sources jar is created.</li>
</ul>
<h2>0.23.2</h2>
<ul>
<li>Fix signing when using Gradle 8.0.</li>
<li>Finding a matching staging profile in Sonatype is more lenient. If there is just one that one will always be used.
The plugin will also fallback to any staging profile that has a matching prefix with the group id.</li>
<li>As a workaround for an issue in Gradle that causes invalid module metadata for <code>java-test-fixtures</code> projects, <code>project.group</code>
and <code>project.version</code> are now being set again for those projects. <a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/pull/490">https://github.com/facebook/flipper/issues/490</a></li>
</ul>
<h2>0.23.1</h2>
<p><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/blob/master/CHANGELOG.md#version-0231-2022-12-30">Changelog</a></p>
<h2>0.23.0</h2>
<p><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/blob/master/CHANGELOG.md#version-0230-2022-12-29">Changelog</a></p>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/vanniktech/gradle-maven-publish-plugin/blob/main/CHANGELOG.md">com.vanniktech:gradle-maven-publish-plugin's changelog</a>.</em></p>
<blockquote>
<h2>0.24.0 <em>(2023-01-29)</em></h2>
<ul>
<li>Support arbitrary Sonatype hosts instead of just oss.sonatype.org and s01.oss.sonatype.org.</li>
<li>Support adjusting timeouts for Sonatype related requests and operations. <a href="https://vanniktech.github.io/gradle-maven-publish-plugin/central/#timeouts">See docs</a></li>
<li>Internal change on how the sources jar is created.</li>
</ul>
<h2>0.23.2 <em>(2023-01-17)</em></h2>
<ul>
<li>Fix signing when using Gradle 8.0.</li>
<li>Finding a matching staging profile in Sonatype is more lenient. If there is just one that one will always be used.
The plugin will also fallback to any staging profile that has a matching prefix with the group id.</li>
<li>As a workaround for an issue in Gradle that causes invalid module metadata for <code>java-test-fixtures</code> projects, <code>project.group</code>
and <code>project.version</code> are now being set again for those projects. <a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/pull/490">https://github.com/facebook/flipper/issues/490</a></li>
</ul>
<h2>0.23.1 <em>(2022-12-30)</em></h2>
<ul>
<li>Also support publishing sources for the <code>java-test-fixtures</code> plugin in Kotlin/JVM projects.</li>
<li>Suppress Gradle warnings when publishing a project that uses <code>java-test-fixtures</code>.</li>
</ul>
<h2>0.23.0 <em>(2022-12-29)</em></h2>
<p>Updated docs can be found on <a href="https://vanniktech.github.io/gradle-maven-publish-plugin/">the new website</a>.</p>
<ul>
<li><strong>NEW</strong>: It is now possible to set group id, artifact id directly through the DSL
<pre lang="groovy"><code>mavenPublishing {
  coordinates(&quot;com.example&quot;, &quot;library&quot;, &quot;1.0.3&quot;)
}
</code></pre>
</li>
<li><code>project.group</code> and <code>project.version</code> will still be used as default values for group and version if the
<code>GROUP</code>/<code>VERSION_NAME</code> Gradle properties do not exist and <code>coordinates</code> was not called, however there are 2
<strong>behavior changes</strong>:
<ul>
<li>The <code>GROUP</code> and <code>VERSION_NAME</code> Gradle properties take precedence over <code>project.group</code> and <code>project.version</code> instead
of being overwritten by them. If you need to define the properties but replace them for some projects,
please use the new <code>coordinates</code> method instead.</li>
<li>The <code>GROUP</code> and <code>VERSION_NAME</code> Gradle properties will not be explicitly set as <code>project.group</code> and
<code>project.version</code> anymore.</li>
</ul>
</li>
<li><strong>NEW</strong>: Added <code>dropRepository</code> task that will drop a Sonatype staging repository. It is possible to specify
which repository to drop by adding a <code>--repository</code> parameter with the id of the staging repository that was
printed during <code>publish</code>. If no repository is specified and there is only one staging repository, that one
will be dropped.</li>
<li>Added workaround to also publish sources for the <code>java-test-fixtures</code> plugin</li>
<li>Fixed publishing Kotlin/JS projects with the base plugin.</li>
<li>Fixed that a POM configured through the DSL is incomplete when publishing Gradle plugins.</li>
<li>The minimum supported Gradle version has been increased to 7.3.</li>
<li>The plugin now requires using JDK 11+ to run Gradle.</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="7faa441d3a"><code>7faa441</code></a> Prepare changelog for release 0.24.0.</li>
<li><a href="95f5b4eb79"><code>95f5b4e</code></a> make timeouts configurable (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/508">https://github.com/facebook/flipper/issues/508</a>)</li>
<li><a href="4b4302027a"><code>4b43020</code></a> replace custom sources jar task (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/507">https://github.com/facebook/flipper/issues/507</a>)</li>
<li><a href="744db566a1"><code>744db56</code></a> Update dependency org.jlleitschuh.gradle:ktlint-gradle to v11.1.0 (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/506">https://github.com/facebook/flipper/issues/506</a>)</li>
<li><a href="f041faa59d"><code>f041faa</code></a> Open up SonatypeHost (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/504">https://github.com/facebook/flipper/issues/504</a>)</li>
<li><a href="9300a2be9c"><code>9300a2b</code></a> Update dependency com.vanniktech:gradle-maven-publish-plugin to v0.23.2 (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/501">https://github.com/facebook/flipper/issues/501</a>)</li>
<li><a href="8f3edf1e75"><code>8f3edf1</code></a> Update CHANGELOG for 0.23.2.</li>
<li><a href="b944e0d46a"><code>b944e0d</code></a> test against Gradle 8.0-rc-2 and AGP 8.0.0-alpha11 (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/499">https://github.com/facebook/flipper/issues/499</a>)</li>
<li><a href="93a21886fa"><code>93a2188</code></a> make finding a staging profile more lenient (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/498">https://github.com/facebook/flipper/issues/498</a>)</li>
<li><a href="6686704e1d"><code>6686704</code></a> Update dependency com.android.tools.build:gradle to v7.4.0 (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/495">https://github.com/facebook/flipper/issues/495</a>)</li>
<li>Additional commits viewable in <a href="https://github.com/vanniktech/gradle-maven-publish-plugin/compare/0.22.0...0.24.0">compare view</a></li>
</ul>
</details>
<br />

[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=com.vanniktech:gradle-maven-publish-plugin&package-manager=gradle&previous-version=0.22.0&new-version=0.24.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

 ---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `dependabot rebase` will rebase this PR
- `dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `dependabot merge` will merge this PR after your CI passes on it
- `dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `dependabot cancel merge` will cancel a previously requested merge and block automerging
- `dependabot reopen` will reopen this PR if it is closed
- `dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

Pull Request resolved: https://github.com/facebook/flipper/pull/4511

Reviewed By: ivanmisuno

Differential Revision: D43303376

Pulled By: passy

fbshipit-source-id: f434a912d246bb7e916d0afb2ee9cf3a5d8bd8d4
2023-02-15 09:30:06 -08:00
2023-02-15 08:27:19 -08:00
2023-02-15 03:55:28 -08:00
2023-02-10 09:48:48 -08:00
2023-01-10 06:14:43 -08:00
2023-02-15 06:01:09 -08:00
2020-07-08 07:10:46 -07:00
2020-11-09 08:24:28 -08:00
2020-03-26 05:53:53 -07:00
2022-09-12 03:48:43 -07:00
2019-09-30 06:41:57 -07:00
2018-06-01 11:03:58 +01:00
2020-04-14 09:21:58 -07:00
2018-07-31 08:15:12 -07:00
2019-08-29 23:21:14 -07:00
2020-11-09 08:24:28 -08:00
2022-02-16 08:22:09 -08:00
2022-02-16 08:22:09 -08:00
2022-12-05 07:57:16 -08:00
2022-02-25 02:33:22 -08:00
2020-08-10 08:47:32 -07:00

logo

Flipper

Android Maven Badge iOS

Flipper (formerly Sonar) is a platform for debugging mobile apps on iOS and Android and JS apps in your browser or in Node.js. Visualize, inspect, and control your apps from a simple desktop interface. Use Flipper as is or extend it using the plugin API.

Flipper

Table of Contents

Mobile development

Flipper aims to be your number one companion for mobile app development on iOS and Android. Therefore, we provide a bunch of useful tools, including a log viewer, interactive layout inspector, and network inspector.

Extending Flipper

Flipper is built as a platform. In addition to using the tools already included, you can create your own plugins to visualize and debug data from your mobile apps. Flipper takes care of sending data back and forth, calling functions, and listening for events on the mobile app.

Contributing to Flipper

Both Flipper's desktop app, native mobile SDKs, JS SDKs are open-source and MIT licensed. This enables you to see and understand how we are building plugins, and of course, join the community and help to improve Flipper. We are excited to see what you will build on this platform.

In this repo

This repository includes all parts of Flipper. This includes:

  • Flipper's desktop app built using Electron (/desktop)
  • native Flipper SDKs for iOS (/iOS)
  • native Flipper SDKs for Android (/android)
  • React Native Flipper SDK (/react-native)
  • JS Flipper SDK (/js)
  • Plugins:
    • Logs (/desktop/plugins/public/logs)
    • Layout inspector (/desktop/plugins/public/layout)
    • Network inspector (/desktop/plugins/public/network)
    • Shared Preferences/NSUserDefaults inspector (/desktop/plugins/public/shared_preferences)
  • website and documentation (/website / /docs)

Getting started

Please refer to our Getting Started guide to set up Flipper. Or, (still experimental) run npx flipper-server for a browser based version of Flipper.

Requirements

  • node >= 8
  • yarn >= 1.5
  • iOS developer tools (for developing iOS plugins)
  • Android SDK and adb

Building from Source

Desktop

Running from source

git clone https://github.com/facebook/flipper.git
cd flipper/desktop
yarn
yarn start

NOTE: If you're on Windows, you need to use Yarn 1.5.1 until this issue is resolved.

Building standalone application

Provide either --mac, --win, --linux or any combination of them to yarn build to build a release zip file for the given platform(s). E.g.

yarn build --mac --version $buildNumber

You can find the resulting artifact in the dist/ folder.

iOS SDK + Sample App

cd iOS/Sample
rm -f Podfile.lock
pod install --repo-update
open Sample.xcworkspace
<Run app from xcode>

You can omit --repo-update to speed up the installation, but watch out as you may be building against outdated dependencies.

Android SDK + Sample app

Start up an android emulator and run the following in the project root:

./gradlew :sample:installDebug

React Native SDK + Sample app

Requires RN 0.69+!

cd react-native/ReactNativeFlipperExample
yarn
yarn android

Note that the first 2 steps need to be done only once.

Alternatively, the app can be started on iOS by running yarn ios.

If this is the first time running, you will also need to run pod install --repo-update from the react-native/ReactNativeFlipperExample/ios folder.

React Native Windows (Experimental)

An experimental version of Flipper for React Native Windows is available. The following steps prepare the React Native Flipper project:

cd react-native/react-native-flipper
vcpkg install openssl:x64-uwp openssl:arm-uwp
vcpkg integrate install
yarn install
cd windows
nuget install ReactNativeFlipper/packages.config

In a nutshell, vcpkg is used to install OpenSSL. Nuget is used to install Boost.

Then, the sample application can be built and run as follows:

cd ../../ReactNativeFlipperExample
yarn install
yarn relative-deps
npx react-native run-windows

At the moment there's no available package for React Native Flipper. This means that to integrate Flipper with any other existing applications, an explicit reference to the project needs to be added just as is done with the sample application.

JS SDK + Sample React app

cd js/react-flipper-example
yarn
yarn start

Troubleshooting

Older yarn versions might show an error / hang with the message 'Waiting for the other yarn instance to finish'. If that happens, run the command yarn first separately in the directory react-native/react-native-flipper.

Documentation

Find the full documentation for this project at fbflipper.com.

Our documentation is built with Docusaurus. You can build it locally by running this:

cd website
yarn
yarn start

Contributing

See the CONTRIBUTING file for how to help out.

License

Flipper is MIT licensed, as found in the LICENSE file.

Description
No description provided
Readme 106 MiB
Languages
TypeScript 61.2%
Java 9.9%
Objective-C 7%
Kotlin 5.8%
C++ 4.8%
Other 11.2%