New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

react.rt

Package Overview
Dependencies
Maintainers
1
Versions
7
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

react.rt - npm Package Compare versions

Comparing version 0.1.0 to 0.1.1

13

package.json
{
"name": "react.rt",
"version": "0.1.0",
"version": "0.1.1",
"description": "React Release/Feature Toggle",
"keywords": [
"react.rt",
"react",
"release",
"feature",
"toggle",
"switch",
"rt"
],
"homepage": "https://github.com/NShahri/React.ReleaseToggle",
"bugs": "https://github.com/NShahri/React.ReleaseToggle/issues",
"main": "dist/index.umd.js",

@@ -6,0 +17,0 @@ "jsnext:main": "dist/index.js",

23

README.md

@@ -42,2 +42,3 @@ # React.RT

You can use ReleaseToggleApp to define enabled/disabled features for all children.
You can use ReleaseToggle to check if features are matched to specified condition.

@@ -93,2 +94,3 @@

If you want to display context on your application you can use CurrentTogglesView.
We do not recomment to use this component in your production release, but it can be useful for testing purposes.

@@ -128,12 +130,19 @@

### backlog
1. using cookies to get list of features
2. using query string for list of features
3. implementing versioning for features, ie: feature1: '~1.0.2'
4. supporting different engine for checking features
5. server side supporting
### Future works
1. Documentation (in progress)
1. Moe unit tests (in progress)
1. Using build server
1. Fixing bower package
1. Publishing es6 and umd of each modules which can be used in any other application build process
1. Using cookies to get list of features
1. Using query string for list of features
1. Implementing versioning for features, ie: feature1: '~1.0.2'
1. Supporting different engine for checking features
1. Server side supporting
### Contributing
Use [GitHub issues](https://github.com/NShahri/React.ReleaseToggle/issues) for requests.
We expect project participants to adhere to [Code of Conduct]().
I actively welcome pull requests.
I expect project participants to adhere to [Code of Conduct]().
Please read the full text so that you can understand what actions will and will not be tolerated.

@@ -140,0 +149,0 @@

Sorry, the diff of this file is too big to display

Sorry, the diff of this file is too big to display

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc