Common stuff used in my projects
XML-Tools Common Utilities
Node.js library for Backstage CLIs
Commonly used shared functionality and types to support inquirer modules.
This is the Node.js wrapper of the runtime-agnostic [`@shopify/theme-check-common`](https://npm.im/@shopify/theme-check-common) package. It comes with batteries included.
Core module exporting shared interfaces, AST node definitions, and common utilities for Herb
Returns an array containing the initial elements which both input arrays have in common
Shared utilities for DefinitelyTyped tools
a few common utility template tags for ES2015
Openapi tools common libraries
Utilities for SQL instrumentations
Redis utilities for redis instrumentations
This is the Node.js wrapper of the runtime-agnostic [`@shopify/theme-language-server-node`](https://npm.im/@shopify/theme-language-server-common) package. It comes with batteries included.
React Common package delivers common utilities that can be used with the KendoReact UI components. KendoReact Common Utilities package
Microsoft Authentication Library for js
A common tooling library used by the googleapis npm module. You probably don't want to use this directly.
TypeSpec Azure Resource Manager library
Syntax tree data structure and parser interfaces for the lezer parser
Common functionality for ts-morph packages.
Common components for Cloud APIs Node.js Client Libraries
Find the common ancestor of 2 or more paths on Windows or Unix
Storybook framework-agnostic API
Core types and classes for Google services.
A tool which installs common Rake tasks, Gem dependencies, and RSpec Helpers used in my gems.
My Rails apps need few common tools. This gem extracts them into a single place.
Now FLOSS is so common that even Microsoft use it and develop it. But do you have control over your tools for daily use? Building your own tools is the best way to develop software, and Ruby is the best language for such use. In this talk, I introduce my own tools and my development style.
Back in 2015 I was a guy automating things at my job and two scripts had a common need -- they both had to pass the same credentials to Jenkins (via query params, I guess). That common tool with a single method was a Net::HTTP wrapper -- that's where the name from. Then when the third script appeared two of them had to pass the Basic Auth. The verb POST was added and common logging format, and relatively complex retry logic. Then some website had redirects and I had to store cookies, then GZIP and API rate limits... I was not going to gemify this monster but it is now a dependency in many other gems, and since Gemfile does not support Github dependencies I have to finally gemify it.
<p>Sass or the much better approach of scss is really helpful and a big silver bullet for my css structuring in ruby projects.</p> \ <p>Standard sass command works for whole directories or single files only. In general it gets the jobs we want done, but in practical usage i think the sass command tool is a little bit unconvinient. A common scenario for me is, \ that you have whole bunch of sass files, which you want to compile to a single compressed output file. But if you have splitted your sass files in component based modules and you want to watch the complete folder you have to care for dependency handling in each file, because each file will be compiled for its own.</p> \ <pre># compiling a complete folder with scss ~ $ sass css/scss:css/compiled</pre> \ <p>So converting the whole folder is not what i want, because i don\'t want to import for example my color.sass config file in each module again. Compiling a single file seems to be the better solution, and it works in general, as expected, but the devil is in the detail. </p> <pre># compiling a single file where the other files are imported. ~ $ sass css/scss/main.scss:css/compiled/main.css</pre> \ <p>If we change a file with impact to our main.sass file, the --watch handle will not get it, because it observes only the timestamp of the given main.sass.</p> <p>Here is it, where mindful_sass tries to help out. You use it according to the single file variant of sass, but it tries to observe the whole folder the given sass file is placed. If a timestamp of file in the sass folder or its children changes it will compile the specified main.sass again.</p> \ <p>This gem is not aimed to replace anything in the sass universe. It is only a wrapper to avoid the described unconvinience, and i hope that it gets useless as fast as possible, because the sass development gets this feature done for themselves.</p> \ <p>Thanks anyway to the sass developer team.</p>