An empty state appears when there is no data to display and describes what the user can do next.
Dependency-aware todo manager — tasks as a DAG, topological sort tells you what to do next
figure for nextjs projects loading contentful images
Mock implementation of the Next.js Router
Curated addons to bring out the best of Storybook
Find package.json files in parent directories, keep finding until you find the right one using iterators.
Sanity.io toolkit for Next.js
Provides low-level interfaces and helper methods for tracing in Azure SDK
Webpack loader that resolves relative paths in url() statements based on the original source file
An AI terminal copilot that runs your command and tells you what to do next when it fails.
Split email messages into an object stream
ESLint plugin for Next.js.
Core library for interfacing with AutoRest generated code
Build chainable fluent interfaces the easy way... with a freakin' chainsaw!
Analytics Next (aka Analytics 2.0) is the latest version of Segment’s JavaScript SDK - enabling you to send your data to any tool without having to learn, test, or use a new API every time.
An **EXPERIMENTAL** Webpack plugin to enable "Fast Refresh" (also previously known as _Hot Reloading_) for React components.
Polyfill for IE/Node 8 for Symbol.asyncIterator
An asynchronous do-while-like function
Provides a cleaner API for enabling and configuring plugins for next.js
Easy way to make a Readable Stream
to do next to next operation on field
Symbol.observable ponyfill
This is the **x86_64-unknown-linux-gnu** binary for `@next/swc`
An abstraction for themes in your React app.
I got sick of doing this test in interviews, so next time someone asks me to do so, I'm going to instead hand them a business card with a URL for this gem on it.
jekyll-category-aware-prev-next adds category aware cat_next and cat_previous to posts since jekyll's next and prev do not take the category into account
Gem helps to do next things with your objects - check the type, make a conversions and work with hashes
From lazy loading, to inline image contents, to fetching unknown width and height, to next generation image formats, this gem aims to extend the default image_tag method to do more for static web pages.
Help the user get to a place where the speedy F8/F10/F11/etc keys work. == Pry F-Keys [+F4+] ls -l (show all locally-defined variables and values) [+F5+] whereami (show the code context) [+F6+] up (a frame, depends on pry-stack_explorer, as does the next one) [+F7+] down [+F8+] continue (depends on pry-debugger, as do step/next/finish) [+Shift-F8+] try-again (restart from last 'raise', depends on pry-rescue) [+F10+] next (run the current statement) [+F11+] step (step into the next method call) [+Shift-F11+] finish (get back out of the last 'step')
Additional finders for capybara that for some reason cannot use only xpath for finding nodes but needs to execute js for some calculations. \ Ex: I you want to find a table cell that is under or next to other cell the easiest way to do it is to check their position on page and compare them. This way you do not need to wory about calculating the effects of using colspan and rowspan attributes. The downside is that you need to use capybara driver that runs a browser like selenium.
Whenever I loop through an array, there are times I wish I could know what comes before or after the item I am currently one. Including prev/next index calculations. This gem helps you with that. However, it would be better for you to create your own since you will probably not like my way of doing it.
Enhanced show-doc (a.k.a ? command) for: $! $" $$ $& $' $* $+ $, $-0 $-F $-I $-K $-W $-a $-d $-i $-l $-p $-v $-w $. $0 $1 $2 $3 $4 $5 $6 $7 $8 $9 $: $; $< $= $> $? $@ $DEBUG $FILENAME $KCODE $LOADED_FEATURES $LOAD_PATH $PROGRAM_NAME $SAFE $VERBOSE $\ $_ $` $stderr $stdin $stdout $~ $⁄ BEGIN END __ENCODING__ __FILE__ __LINE__ alias and begin break case class def defined? do else elsif end ensure false for if in module next nil not or redo rescue retry return self super then true undef unless until when while yield
State machines are awesome but sometimes you need a little more. Like who should do what in order for it to move on? How many steps are left? How can I restfully trigger the next event? Self Control adds route helpers, controller actions and a dsl to turn your existing state machines into full workflows. It is designed to use rails 3 with ActiveModel and should work with any state machine with just a few extra methods.
== Synopsys Class-level configuration DSL == Installation gem install config_accessor == Examples require 'config_accessor' class Remote configurable! config_accessor :host, :default => "localhost" config_accessor :port, :default => "80", :transform => :to_i config_accessor :proxy_host, :proxy_port end class Local < Remote config_accessor :l_port end Remote.host # => "localhost" Remote.port # => 80 Remote.proxy_host # => nil r = Remote.new r.port = "81" r.port # => 81 Remote.port # => 80 Remote.port = 82 # next expressions are equivalent r.port # => 81 r.config[:port] # => 81 r.config["port"] # => 81 r.config.port # => 81 # It supports inheritance, subclasses cannot change superclasses configurations Local.port # => 80 # You can do it with +configure+ method Local.configure do port 81 end # or Local.configure do |config| config.port 81 end
ZenTest provides 4 different tools: zentest, unit_diff, autotest, and multiruby. zentest scans your target and unit-test code and writes your missing code based on simple naming rules, enabling XP at a much quicker pace. zentest only works with Ruby and Minitest or Test::Unit. There is enough evidence to show that this is still proving useful to users, so it stays. unit_diff is a command-line filter to diff expected results from actual results and allow you to quickly see exactly what is wrong. Do note that minitest 2.2+ provides an enhanced assert_equal obviating the need for unit_diff autotest is a continous testing facility meant to be used during development. As soon as you save a file, autotest will run the corresponding dependent tests. multiruby runs anything you want on multiple versions of ruby. Great for compatibility checking! Use multiruby_setup to manage your installed versions. *NOTE:* The next major release of zentest will not include autotest (use minitest-autotest instead) and multiruby will use rbenv / ruby-build for version management.
abstract_feature_branch is a Ruby gem that provides a unique variation on the Branch by Abstraction Pattern by Paul Hammant and the Feature Toggles Pattern by Martin Fowler to enhance team productivity and improve software fault tolerance. It provides the ability to wrap blocks of code with an abstract feature branch name, and then specify in a configuration file which features to be switched on or off. The goal is to build out upcoming features in the same source code repository branch (i.e. Continuous Integration and Trunk-Based Development), regardless of whether all are completed by the next release date or not, thus increasing team productivity by preventing integration delays. Developers then disable in-progress features until they are ready to be switched on in production, yet enable them locally and in staging environments for in-progress testing. This gives developers the added benefit of being able to switch a feature off after release should big problems arise for a high risk feature. abstract_feature_branch additionally supports Domain Driven Design's pattern of Bounded Contexts by allowing developers to configure context-specific feature files if needed. abstract_feature_branch is one of the simplest and most minimalistic "Feature Flags" Ruby gems out there as it enables you to get started very quickly by simply leveraging YAML files without having to set up a data store if you do not need it (albeit, you also have the option to use Redis as a very fast in-memory data store).
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.