Vite resolver for TypeScript compilerOptions.paths
Load node modules according to tsconfig paths, in run-time or via API.
Compiles your TS app and restarts when files are modified.
Get paths for storing things like data, config, cache, etc
Get the first path that exists on disk of multiple paths
Load modules according to tsconfig paths in webpack.
Enforces module path case sensitivity in Webpack
Simple development http server with live reload capability
Minimal and efficient cross-platform file watching library
Determine (XDG-compatible) paths for storing application files (cache, config, data, etc)
Convert Windows backslash paths to slash paths
Determine common OS/platform paths (home, temp, ...)
Tests whether one path is inside another path
UnRS Resolver Node API
If it works, why use something else?
Universal filesystem path utils
very fast object redaction
Determine two file paths are equal
Upgrade your npm scripts to make them smarter and more efficient
Extends `minimatch.match()` with support for multiple patterns
walk paths fast and efficiently
Runs (webpack) loaders
Get the paths of edge browser easily
simple development http server with live reload capability
Protocol-agnostic file watching across local, SSH, FTP, and HTTP
A simple command line utility to cache output of commands
Scan a set of pathnames for file changes according to check sums. Occasionally useful when you need act when some set of files changes.
This gem leverages Guard's watch ability to insert files inline within another file. When the parser incounters a //= path/to/file, it then gets the content of that file and then inserts the content replacing the comment. Optionally that file can then be passed through Uglifier. Files with no insertions will just be copied over.
Creates an Xcode project from a pebble project that contains the needed search paths, resources and .c files to start right away. Each time you build your watch app from the IDE, all warnings and errors of the underlying ´pebble build` command will be presented right in the editor. With AppCode you can even build, install the .pbw to your watch, and look at the live logs as a one-step action directly from your IDE!
# Footman This gem is still growing. ## Installation Depends upon having reprepro tool installed (if debian based) or createrepo installed (if red hat based). Ruby 1.9.+ is required to use this gem. 'createrepo' (rpm) tool does not require any pre-setup to the repository or watched directory. - - - 'reprepro' (deb) tool requires pre-setup. The repository directory for deb files must contain: <pre><code> conf/ conf/distributions conf/options conf/override.precise </pre></code> options file is empty, but needed to make reprepro happy distributions file will contain: <pre><code>Origin: Tyler Label: Tyler's Personal Debs Codename: precise Architectures: i386 amd64 source lpia Components: main Description: Tylers Personal Debian Repository DebOverride: override.precise DscOverride: override.precise Origin: Tyler Label: Tyler's Personal Debs Codename: lenny Architectures: i386 amd64 source lpia Components: main Description: Tylers Personal Debian Repository DebOverride: override.lenny DscOverride: override.lenny </code></pre> Note that the code name is for each distribution repository you support. for each distribtuion repository you support there must be an override file. override file can be left empty, footman will fill it out when a new package is added. The watched directory must have sub directorys named after each of the distribution repositories you support. For example my watched directory at /path/ will have two subdirectories: <pre><code>/path/lenny/ /path/precise/</code></pre> Packages must be dropped into the subdirectory that corrosponds with the distribution they were built on. - - - Add this line to your application's Gemfile: gem 'footman' And then execute: $ bundle Or install it yourself as: $ gem install footman Or locally: $ gem build footman.gemspec $ gem install footman --local ## Usage footman path/to/watch path/to/repo ## Contributing 1. Fork it 2. Create your feature branch (`git checkout -b my-new-feature`) 3. Commit your changes (`git commit -am 'Add some feature'`) 4. Push to the branch (`git push origin my-new-feature`) 5. Create new Pull Request
# Otto AsciiDoc-powered static site generator with Jekyll-style conventions: layouts, includes, data files, posts, drafts, permalinks, and custom collections. ## Install ```sh gem install ottogen ``` Requires Ruby 3.0 or newer. ## Quickstart ```sh mkdir mysite && cd mysite otto init otto build otto serve open http://127.0.0.1:8778/ ``` For a longer walkthrough including AsciiDoc syntax, see [GUIDE.md](GUIDE.md). ## Commands | Command | Description | |---|---| | `otto init [DIR]` | Scaffold a new site (current dir if omitted) | | `otto build` | Render the site to `_build/` | | `otto build --drafts` | Include posts from `_drafts/` | | `otto watch` | Rebuild on file change | | `otto serve` | Serve `_build/` on port 8778 | | `otto generate PAGE` | Create a new page in `pages/` | | `otto post "Title"` | Create a new dated post in `_posts/` | | `otto clean` | Delete `_build/` | | `otto doctor` | Sanity-check project layout | ## Project layout ``` my-site/ ├── .otto # marker ├── config.yml # site config ├── assets/ # copied verbatim into _build/ ├── pages/ # AsciiDoc pages, output mirrors path ├── _layouts/ # ERB layouts (.html.erb) ├── _includes/ # ERB partials ├── _data/ # YAML/JSON files exposed as site.data.* ├── _posts/ # YYYY-MM-DD-slug.adoc └── _drafts/ # undated drafts (excluded by default) ``` ## Configuration (`config.yml`) ```yaml title: My Otto Site description: Things I write url: https://example.com baseurl: "" permalink: /:year/:month/:day/:slug/ collections: recipes: output: true ``` `permalink` accepts these tokens: `:year`, `:month`, `:day`, `:slug`, `:title`. Templates ending in `/` produce pretty URLs (`<path>/index.html`). ## Pages and posts Both support YAML front matter: ```adoc --- layout: default title: Hello tags: [ruby, cli] --- = Hello Welcome to {site_title}. This page is at {page_url}. ``` Pages live under `pages/`; posts under `_posts/` with `YYYY-MM-DD-slug.adoc` names. Layouts wrap rendered AsciiDoc; partials in `_includes/` are pulled in via `<%= partial 'header.html' %>`. ## License MIT