Compile all .ejs files under a directory
fdx component compile tools
Require hook for automatic V8 compile cache persistence
The vue component compile core support vue1 and vue2
Require hook for automatic V8 compile cache persistence
Template compiler package
Stringify your JSON at max speed
SDK for building AI agents with Claude Code's capabilities. Programmatically interact with Claude to build autonomous agents that can understand codebases, edit files, and execute workflows.
MDXv2 to CSF webpack compiler and loader
Test React components using Cypress
Android UiAutomator and Chrome support for Appium
Browser-based Component Testing for Vue.js with Cypress.io
Compiles an evaluating function for a C expression
MDXv1 to CSF webpack compiler and loader
Compile ES2015 computed properties to ES5
Compile ES2015 default and rest parameters to ES5
Compile ES2015 classes to ES5
AI-driven Code Generation and Source Analysis Web Component
Compile ES2015 sticky regex to an ES5 RegExp constructor
Compile ES2015 shorthand properties to ES5
Compile ES2015 block scoping (const and let) to ES5
Compile ES2015 destructuring to ES5
Compile ES2015 spread to ES5
Compile ES2015 unicode string and number literals to ES5
Vue component compiler
Ejs to Javascript compiler.
An HTML-like template language that compiles to Ruby render calls. JSX for Rails.
A meta-gem for the Rubinius components that compile Ruby source code to bytecode.
Redson is a browser based MVC component framework written in Ruby using the Opal ruby-to-js compiler.
Write reactive UI component with Ruby's elegancy and compiled to run in Javascript.
Rack middleware for compiling and serving VueJS single file components
Write reactive UI component with Ruby's elegancy and compiled to run in Javascript.
Rubinius::ToolSet provides a registry for code tools. These include the Rubinius bytecode compiler and parser. These, in turn, depend on other components like the AST and bytecode emitter and serializer. ToolSets provide a mechanism for other languages to reuse as much of the Rubinius code tools as are suitable for that language.
<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>
The Castle MicroKernel is an inversion of control container that was designed towards extensibility. It combines facilities to grow orthogonally. These facilities work side-by-side, without interfering or depending on each other, to allow you to easily extend the container functionality by plugging in new concerns and semantics. You can use it as an embeddable container on tools that support extensions or plugin support, such as tools which exposes configurable pipelines or compilers. The container is set up and configured through code, and can be extended to work with a configuration system that your project supports. Castle Windsor aggregates the MicroKernel and exposes a powerful configuration support. It is suitable for common enterprise application needs. It is able to register facilities and components based on the configuration and adds support for interceptors.
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.