a watchify plugin, provides to re bundle only when files changed
In-depth bundle analyzer for webpack(bundle size, assets, modules, packages)
Build tool and bindings loader for node-gyp that supports prebuilds
A little library for asserting types and values, with zero dependencies.
No description provided.
A lightweight font data library — fontkit’s little sibling
Build tool and bindings loader for node-gyp that supports prebuilds
A lightweight cache for file metadata, ideal for processes that work on a specific set of files and only need to reprocess files that have changed since the last run
Tells you whether or not dependencies in package.json have been changed.
Get bundle name from a bundle identifier (macOS): `com.apple.Safari` → `Safari`
In-depth bundle analyzer for webpack(bundle size, assets, modules, packages)
No description provided.
In-depth bundle analyzer for webpack(bundle size, assets, modules)
Bundled types to instantiate the Polkadot JS api with a Moonbeam network
The same useRef, but with callback
Webpack plugin and CLI utility that represents bundle content as convenient interactive zoomable treemap
ECMAScript code generator
Analyzes each PR's impact on your next.js app's bundle size and displays it using a comment
bundle and require a file
Sigstore bundle type
ReDoc's Command Line Interface
In-depth bundle analyzer for webpack(bundle size, assets, modules)
A simple hook to debug various Reactjs hooks which supports dependency as the second argument.
Delightful JavaScript Testing.
A tool to change the bundle identifier of an Xcode project
Automatically bundle and migrate your Rails app when switching branches, merging upstream changes, and bisecting.
Simplify the management of a sandbox database that can sync content to a production database. Content changes can be bundled to allow partial syncs of the database.
After running bundle update, git-bundlecompare opens the GitHub compare view for each changed git repository.
The `gem local` command allows you to track, change, update per-project usage of `bundle config local.<gem>` settings.
Runs a bundle upgrade, shows the changelog for each gem that was upgraded, and outputs a summary view of gem changes plus their impact.
By requesting trigger build to Wercker with an environment variable which instruct wercker.yml to execute this script, bundle update is invoked, then commit changes and send pull request to GitHub repository if there some changes exist.
# Sambot Sambot is our internal Platform Engineering toolchain to help standardize and simplify our DevOps workflow. It provides an executable with a variety of commands, grouped in various areas of functionality such as session management, DNS changes and cookbook management. ## Usage To install the gem, simply run `chef gem install sambot`. This will install the gem in your ChefDK installation. If you want to use it outside Chef, run `gem install sambot`. Run `chef exec sambot` to be shown the help menu. For help on specific commands, i.e. cookbook management and specific cookbook management commands, run `chef exec sambot help cookbook` or `chef exec sambot cookbook help generate` for example. ## Contributing Bug reports and pull requests are welcome on GitHub at https://github.exacttarget.com/ads-devops/sambot. ### Installation Make sure you have `ruby >= 2.4.0` installed. Install `bundler >= 1.15.1` by running `gem install bundler` Run `bundle install` from the root of the project to install the required Ruby gems. ### Running Sambot If you want to test your changes locally, you can run `bundle exec bin/sambot`. ### Running Tests Run `bundle exec rspec spec` to execute the unit tests. Run `cd integration_tests && bundle exec rspec .` to execute the integration tests. These require that you have Docker Compose available. ### Linting There is nothing here yet
react-manifest-rails automatically generates per-controller Sprockets manifest files for Rails applications using react-rails + Sprockets. It eliminates the monolithic application.js by creating lean, controller-specific ux_*.js bundles, watches for file changes in development, and provides a smart react_bundle_tag view helper that auto-selects the correct bundle per controller.
Simplify the management of a sandbox database that can sync content to a production database. Content changes can be bundled to allow partial syncs of the database.
RSence is a different and unique development model and software frameworks designed first-hand for real-time web applications. RSence consists of separate, but tigtly integrated data- and user interface frameworks. RSence could be classified as a thin server - thick client system. Applications and submobules are installed as indepenent plugin bundles into the plugins folder of a RSence environment, which in itself is a self-contained bundle. A big part of RSence itself is implemented as shared plugin bundles. The user interface framework of RSence is implemented in high-level user interface widget classes. The widget classes share a common foundation API and access the browser's native API's using an abstracted event- and element layer, which provides exceptional cross-browser compatibility. The data framework of RSence is a event-driven system, which synchronized shared values between the client and server. It's like a realtime bidirectional form-submission engine that handles data changes intelligently. On the client, changed values trigger events on user interface widgets. On the server, changed values trigger events on value responder methods of server plugin modules. It doesn't matter if the change originates on client or server, it's all synchronized and propagated automatically. The server framework is implemented as a high-level, modular data-event-driven system, which handles delegation of tasks impossible to implement using a client-only approach. Client sessions are selectively connected to other client sessions and legacy back-ends via the server by using the data framework. The client is written in Javascript and the server is written in Ruby. The client also supports CoffeeScript for custom logic. In many cases, no custom client logic is needed; the user interfaces can be defined in tree-like data models. By default, the models are parsed from YAML files, and other structured data formats are possible, including XML, JSON, databases or any custom logic capable of producing similar objects. The server can connect to custom environments and legacy backends accessible on the server, including software written in other languages.
RSence is a different and unique development model and software frameworks designed first-hand for real-time web applications. RSence consists of separate, but tigtly integrated data- and user interface frameworks. RSence could be classified as a thin server - thick client system. Applications and submobules are installed as indepenent plugin bundles into the plugins folder of a RSence environment, which in itself is a self-contained bundle. A big part of RSence itself is implemented as shared plugin bundles. The user interface framework of RSence is implemented in high-level user interface widget classes. The widget classes share a common foundation API and access the browser's native API's using an abstracted event- and element layer, which provides exceptional cross-browser compatibility. The data framework of RSence is a event-driven system, which synchronized shared values between the client and server. It's like a realtime bidirectional form-submission engine that handles data changes intelligently. On the client, changed values trigger events on user interface widgets. On the server, changed values trigger events on value responder methods of server plugin modules. It doesn't matter if the change originates on client or server, it's all synchronized and propagated automatically. The server framework is implemented as a high-level, modular data-event-driven system, which handles delegation of tasks impossible to implement using a client-only approach. Client sessions are selectively connected to other client sessions and legacy back-ends via the server by using the data framework. The client is written in Javascript and the server is written in Ruby. The client also supports CoffeeScript for custom logic. In many cases, no custom client logic is needed; the user interfaces can be defined in tree-like data models. By default, the models are parsed from YAML files, and other structured data formats are possible, including XML, JSON, databases or any custom logic capable of producing similar objects. The server can connect to custom environments and legacy backends accessible on the server, including software written in other languages.