some tools for Typescript inspired by .NET Framework
Cascades HTTP contract (OpenAPI YAML) for JS/TS tooling — npm companion to the PyPI cascades-sdk Python client.
TS Compiler transformer for formatjs
Create objects, fields, tabs, etc
Tooling which enables you to use TypeScript with ESLint
Interactive setup wizard for TypeScript tooling
Angular Schematics - Library
Find and load configuration from a package.json property, rc file, TypeScript module, and more!
A CLI for formatjs.
OpenRPC Specification Extension Schema
Improve the debugging experience and add server-side rendering support to styled-components
ESLint plugin for formatjs
SAP Fiori Tools – UI5 Tooling
UI5 CLI extensions to transpile code
TypeScript plugin for ESLint
TypeScript scope analyser for ESLint
Lib for CLI for formatjs.
Utilities for working with TypeScript + ESLint together
Type utilities for working with TypeScript + ESLint together
Fast Color Parsing and Manipulation
Standalone TypeScript project service wrapper for linting.
Celo base common utils, no dependencies
An ESLint custom parser which leverages TypeScript ESTree
Utilities for collecting TSConfigs for linting scenarios.
Cartage provides a repeatable means to create a package for a server-side application that can be used in deployment with a configuration tool like Ansible, Chef, Puppet, or Salt. The package is created with vendored dependencies so that it can be deployed in environments with strict access control rules and without requiring development tool presence on the target server(s). This is the last release of cartage. It's been a fun ride, but Docker-based images are our future at Kinetic Commerce. There is one feature that remains useful, the release-metadata output. We have created a new, more extensible format for which we will be creating a gem to manage this. One example of the implementation can be found at: https://github.com/KineticCafe/release-metadata-ts We will also be replacing `cartage-rack` with a new gem supporting this new format.
Command-line tool that automatises photo/video uploads to Flickr. Entering 'flickru <directory>' in your command line, any photos under 'directory' (and subdirs) are uploaded to your Flickr account (interactively entered the first time you start flickru). Photos are identified by case-insensitive extensions: GIF, JPEG, JPG, PNG, and TIFF. Videos are identified by case-insensitive extensions: AVI, MPEG, and MPG. flickru automatically sets the following Flickr metadata: (1) date taken: file last-modification time, unless JPEG/TIFF Exif metadatum 'date_time_original' is found (Flickr understands it natively). (2) privacy policy: private, visible by friends & family, hidden for public searches (3) safety level: safe (4) permissions: friends & family can add comments to the photo and its notes; nobody can add notes and tags to the photo (5) description: for videos longer than 90s (Flickr's longest allowed duration) but shorter than 500MB (Flickr's maximum permisible size), it will contain an annotation about its large duration. (6) title: extracted from the parent directory name (7) geolocation & accuracy: extracted from the parent directory name, unless JPEG/TIFF Exif GPS metadata is found (Flickr understands them natively). Before uploading photos, please, make sure that you have correctly named each photos parent directory according to the name format 'TITLE[@LOCATION[#PRECISION]]', where: (1) TITLE is the desired title for the photos stored in the directory. If no LOCATION is given, flickru tries to extract the location from Wikipedia page TITLE. (2) LOCATION is the location of the photos, specified as: (a) the Wikipedia page name (whitespaces allowed) of the location or (b) its coordinates LATITUDE,LONGITUDE (3) PRECISION is the Flickr geolocation precision. Flickru sets it to one of the following case insentitive literals: 'street', 'city', 'region', 'country', 'world'. Photos are classified into photosets. If the photoset does not exist, flickru creates it. This photoset is named after its grandparent directory. The photoset is arranged by 'date taken' (older first). To see some examples on the directory structure recognised by flickru, please explore the subdirectories under 'var/ts'. GitHub : http://github.com/jesuspv/flickru RubyGems: http://rubygems.org/gems/flickru