React Native Expressive#

This library can also be used as a Git Submodule, which can enable hot reloading of library codes changes.

The tradeoff is the host app is then responsible for including the library's dependencies directly within the host's package.json and configuring any needed aliases to resolve library items from the submodule path.

Install the submodule

git submodule add https://github.com/thehale/react-native-expressive.git lib/react-native-expressive

Install the submodule's dependencies

node ./lib/react-native-expressive/script/install-dependencies-in-host.js

Configure Aliases

babel.config.js

module.exports = {
  plugins: [
+    [
+      'module-resolver',
+      {
+        extensions: ['.ios.js', '.android.js', '.ios.jsx', '.android.jsx', '.js', '.jsx', '.json', '.ts', '.tsx'],
+        root: ['.'],
+        alias: {
+          'react-native-expressive': './lib/react-native-expressive/src',
+        },
+      },
+    ]
  ]
}

tsconfig.json

{
  "compilerOptions": {
    "paths": {
+      "react-native-expressive": ["./lib/react-native-expressive/src"]
    }
  }
}

TL;DR#

You can use files from this project in both open source and proprietary applications, provided you include the above attribution. However, if you modify any code in this project, or copy blocks of it into your own code, you must publicly share the resulting files (note, not your whole program) under the MPL-2.0. The best way to do this is via a Pull Request back into this project.

If you have any other questions, you may also find Mozilla's official FAQ for the MPL-2.0 license insightful.

If you dislike this license, you can contact me about negotiating a paid contract with different terms.

Disclaimer: This TL;DR is just a summary. All legal questions regarding usage of this project must be handled according to the official terms specified in the LICENSE file.

Why the MPL-2.0 license?#

I believe that an open-source software license should ensure that code can be used everywhere.

Strict copyleft licenses, like the GPL family of licenses, fail to fulfill that vision because they only permit code to be used in other GPL-licensed projects. Permissive licenses, like the MIT and Apache licenses, allow code to be used everywhere but fail to prevent proprietary or GPL-licensed projects from limiting access to any improvements they make.

In contrast, the MPL-2.0 license allows code to be used in any software project, while ensuring that any improvements remain available for everyone.