☝️ Create an index for a lib directory
const index = require('index.js')
Serve directory listings
Provides a fallback for non-existing directories so that the HTML 5 history API can be used.
finds an item in an array matching a predicate function, and returns its index
Microsoft sucks
Use sign and abs functions in CSS
Convert a string index to its line and column position
Cyclist is an efficient cyclic list implemention.
ES2015 `Array#findIndex()` ponyfill
Like a Set, but provides the index of the `key` in the backing array
Fixes stack traces for files with source maps
Fixes stack traces for files with source maps
Parse HTTP X-Forwarded-For header
Traverse an ESTree-compliant AST
Find the index to insert an element in array keeping the sort order.
A 2D spatial index for axis-aligned boxes
Recursively iterates over specified directory, require()'ing each file, and returning a nested hash structure containing those modules.
Set of utility macros to make writing N-API modules a little easier.
A very fast static 2D index for points based on kd-tree.
This package provides support for the [RediSearch](https://redis.io/docs/interact/search-and-query/) module, which adds indexing and querying support for data stored in Redis Hashes or as JSON documents with the [RedisJSON](https://redis.io/docs/data-type
TypeScript definitions for serve-index
vendored packages for visx
Example Client -------------- ```js 'use strict' const index = require('slimple-ws'); const WebSocketClient = index.WebSocketClient; const EVENTS = index.EVENTS; const Message = index.Message; var wsc = new WebSocketClient('ws://localhost:90
An easy to use search index (requiring no external servers) with a pluggable design for index storage.
ActiveRecord uniqueness validations without raceconditions
A simple read-only interface to Solr, built on Sunspot. Lunr makes it easy to query and create objects from a Sunspot-managed Solr index without requiring all the knowledge, code, and data used to build the index in the first place. If you have complex indexes with a stored fields and need to search / access those fields without access to the original data store, Lunr might be what you're looking for.
* match_each * match_enum * match_in_order require 'rubygems' require 'spec' require 'gregwebs-rspec_multi_matchers' describe 'array of ones' do it 'should be all ones' do [1,2,3].should each { |n| n.should == 1 } end end =begin output 'array of ones should fail on 2' FAILED line: 14 item 1: 2 expected: 1, got: 2 (using ==) =end As expected, the output shows expected and got fields line is the line number of the expectiation inside the block the item line gives the index of the item being yielded to the block, and the item itself
A simple read-only interface to Solr, built on Sunspot. Lunr makes it easy to query and create objects from a Sunspot-managed Solr index without requiring all the knowledge, code, and data used to build the index in the first place. If you have complex indexes with a stored fields and need to search / access those fields without access to the original data store, Lunr might be what you're looking for.
== Description Proof of concept to maintain a file with sorted and unique values. This could be helpful for building building indexes. Range#bsearch is used to determine if a line is already in the file and to determine where a line should be inserted. This means Ruby 2.0 is required.
to call (gem) require "creates_html_file_test", the creates_html_file_test method has the following arguments, ( content=nil - empty default, title_arg="my page" - set the default title name - "my page" arg="index" - sets the name of the html file by default - "index" bypass_html: false - when false, all html tags are turned off, when true, the code is not changed ) CreatesHtmlFileTest.creates_html_file_test(content=nil, title_arg="my page", arg="index", bypass_html: false)
Scoped search makes it easy to search your ActiveRecord-based models. It will create a named scope :search_for that can be called with a query string. It will build an SQL query using the provided query string and a definition that specifies on what fields to search. Because the functionality is built on named_scope, the result of the search_for call can be used like any other named_scope, so it can be chained with another scope or combined with will_paginate. Because it uses standard SQL, it does not require any setup, indexers or daemons. This makes scoped_search suitable to quickly add basic search functionality to your application with little hassle. On the other hand, it may not be the best choice if it is going to be used on very large datasets or by a large user base.
Embed an AI-powered database chatbot into any Rails application. Auto-discovers your PostgreSQL schema, indexes your codebase, generates SQL from natural language, and streams answers through a chat widget. Zero configuration required.
Shoulda Matchmakers generates regression specs for existing ActiveRecord models and ActionController controllers using Shoulda Matchers. It generates specs for model validations, associations, nested attributes, enum definitions, attribute serialization, database columns and database indexes as well as controller REST routes, and before/after/around actions/filters. It can also generate FactoryGirl factories containing the minimum attributes required for the factory to create a valid object. Shoulda Matchmakers is based on the Regressor gem by Erwin Schens.
deplate is a ruby based tool for converting documents written in an unobtrusive, wiki-like markup to LaTeX, HTML, "HTML slides", or docbook. It supports page templates, embedded LaTeX code, footnotes, citations, bibliographies, automatic generation of an index, table of contents etc. It can be used to create web pages and (via LaTeX or Docbook) high-quality printouts from the same source. deplate probably isn't suited for highly technical documents or documents that require a sophisticated graphical layout. For other purposes it should work fine. deplate aims to be modular and easily extensible. It is the accompanying converter for the Vim viki plugin. In the family of wiki engines, the choice of markup originated from the emacs-wiki.
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.