Offered by bld.ai, `usual-module` is an exclusive npm package forming a component of the Usual.chat application suite. The central feature of this package is the `UsualChat` component, which offers dual functionality. It can be tailored to function as an
An HTTP(s) proxy `http.Agent` implementation for HTTP
JavaScript's functional programming helper library.
Working around a Safari 14 IndexedDB bug
extended POSIX-style sprintf
Posthog-js allows you to automatically capture usage and send events to PostHog.
Seamlessly using Webpack Module Federation with the Angular CLI.
MuPDF.js
A wrapper around the native DataView which can handle multiple ArrayBuffers.
Providing common fields for analytics integrations
A module which provides an implementation of an automation event list.
Retry a request.
Custom fonts mapping module
Honeycomb.io Javascript library
Snyk CLI interface definitions
Run commands concurrently
OpenInference Instrumentation for LangChain.js
Babel helper functions for inserting module loads
Babel helper functions for implementing ES6 module transformations
print the filename and line number of the caller (use only in development environment)
No description provided.
Vue docgen loader for webpack
MetaMask example snap demonstrating the use of WebAssembly and the `endowment:webassembly` permission
Is this specifier a node.js core module?
A port of File::ReadBackwards, the Perl module by Uri Guttman, for reading a file in reverse, line by line. This can often be helpful for things like log files, where the interesting information is usually at the end.
A collection of methods usually implemented in a HSM (Hardware Security Module)
Tiny Singleton is a very simple implementation of the Singleton Design Pattern. Compared to the Singleton module in the stdlib, one does not need to class 'klass.instance' to get access to the singleton object, one can call 'klass.new' as usual. It is thus easier to add the Singleton Pattern to an existing class without changing the way the code calls it.
IfElse is an implementation of the pure object-oriented conditional syntax found in languages of the SmallTalk family, including Self. Those languages distinguish themselves by taking the "everything is an object / everything is a method" approach to a further extreme than Ruby, and getting rid of almost all cases of special syntax other than object definition and method call. Ruby, of course, already works this way for some purposes -- thus most Ruby developers prefer to write [1, 17, 39].each {|x| puts x} rather than for x in [1, 17, 39] puts x end and 3.times {|n| puts n} instead of i = 1 while i <= 3 puts i i += 1 end This module extends that same preference to conditional statements, providing replacements for the Ruby keywords +if+, and +unless+: x = 1 (x >= 0).if {puts 'positive'} (x < 0).unless {puts 'positive'} Note that as with the built-in special forms these methods replace, these methods are available on any Ruby Object, and obey the usual rules of which values are considered "Truthy" and "Falsey". <b>Note that the primary purpose of this gem is to demonstrate that the built-in (special form) versions of conditionals provided with Ruby are mostly syntactic sugar -- as with the +for+ keyword, there is no real need for these to be built into the language. With that said, the gem is fully tested, has no particular performance penalty (beyond the usual cost of method dispatch), and should be fully useable in general purpose code.</b> <b>Note also that while Smalltalk-family languages also provide an equivalent to the Ruby +else+ keyword, this depends on the more general block/lambda capability of those languages, which allow a method to take multiple blocks as arguments. This could be imitated with a syntax like:</b> # NOT A REAL EXAMPLE (x > 42).if then: lambda {|x| :big }, else: lambda {|x| :small} <b>which is true to the SmallTalk original, but feels less Ruby-ish to me, so I didn't implement this -- perhaps in a later version.</b>
This module provides a method for calculate the duration time from a date \nlike reg_date, which is usually used for statistics.\n\nUsage:\n\n # Assume that today is 2013-07-07\n require 'duration_time' \n reg_time = Time.new(2011,8,2,0,0,0, "+08:00")\n # You can use reg_time = Date.parse("2011-08-02") if you have included\n # gem active_support!\n duration_time( reg_time ) \n # => {\n # :years=>[2011, 2012, 2013], \n # :months=>["2011-08", "2011-09", "2011-10", "2011-11", "2011-12", \n # "2012-01", "2012-02", "2012-03", "2012-04", "2012-05", "2012-06", \n # "2012-07", "2012-08", "2012-09", "2012-10", "2012-11", "2012-12", \n # "2013-01", "2013-02", "2013-03", "2013-04", "2013-05", "2013-06"], \n # :quarters=>["2011-09", "2011-12", "2012-03", "2012-06", "2012-09", \n # "2012-12", "2013-03", "2013-06"]\n # }\n\nAnd you can specify default parameter `include_this_month_of_this_year = true`\nif you want to include this month of this year. Default value is `false`.\n
= TMail http://tmail.rubyforge.org/ Mikel Lindsaar maintainer Trans assitant developer Minero Aoki original developer == NOTE: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ! THIS IS A FORK OF TMAIL HACKED TOGETHER TO WORK WITH RUBY 1.9.1 ! ! USE AT YOUR OWN DISCRETION ! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! == DESCRIPTION: TMail is a mail handling library for Ruby. It abstracts a mail message into a usable object allowing you to read, set, add and delete headers and the mail body. TMail is used by the Ruby on Rails web framework as the Email abstraction layer for their ActionMailer module. It is also used by the Nitro framework and many other applications on and off the web. The goal of the TMail handling library is to be able to parse and handle raw Email sources and produce RFC compliant Emails as a result. If you find something that TMail does that violates an RFC, we want to know and we'll get it fixed fast. == DOCUMENTATION: The place you will want to look first is the TMail::Mail class. This has the vast majority of methods you will be using to talk to your TMail object. == FEATURES/PROBLEMS: TMail is fairly RFC compliant on the handling of emails. There are also some problems in the header handling, but for 99.9% of email, you will be fine. Usually, the problems revolve around parsing incomming emails and making sense of them. I really welcome any examples of Emails that "didn't work" with TMail so I can use them as test cases. == SYNOPSIS: TMail is very easy to use. You simply require the library and then pass a raw email text message into the TMail::Mail.parse method. This returns a TMail::Mail object which you can now query and run methods against to modify, inspect or add to the Email. You can find almost all of the methods that you will use to talk to and update a TMail instance in the TMail::Mail class. I am constantly updating this code, with comments, added a fair bit and have a lot more to go!. === Short Version: irb(main):001:0> require 'tmail' irb(main):002:0> raw_email = File.open("my_raw_email", 'r') { |f| @mail = f.read } irb(main):003:0> email = TMail::Mail.parse(raw_email) irb(main):004:0> puts email['to'] mikel@example.com => nil irb(main):005:0> email['to'] = 'mikel@somewhere.else.com' => "mikel@somewhere.else.com" irb(main):006:0> puts email['to'] mikel@somewhere.else.com => nil === Longer Version: Assuming you have a single raw email in the variable my_message, you can do the following: require 'tmail' email = TMail::Mail.parse(my_message) This will give you a TMail::Mail class containing your parsed message. There are other methods of opening emails through Ports. You can view this email by a simple puts: puts email Return-Path: <mikel@nowhere.com> Date: Sun, 21 Oct 2007 19:38:13 +1000 From: Mikel Lindsaar <mikel@nowhere.com> To: mikel@somewhere.com Message-Id: <009601c813c6$19df3510$0437d30a@mikel091a> Subject: Testing Email Hello Mikel Easy right? === Adding a header to the EMail: Say now that you have opened your message, you want to put in a Reply-To field. You do this like so: email['reply-to'] = "My Email Address <my_address@anotherplace.com>" Is it really there? Well, find out with a puts: puts email Return-Path: <mikel@nowhere.com> Date: Sun, 21 Oct 2007 19:38:13 +1000 From: Mikel Lindsaar <mikel@nowhere.com> Reply-To: My Email Address <my_address@anotherplace.com> To: mikel@somewhere.com Message-Id: <009601c813c6$19df3510$0437d30a@mikel091a> Subject: Testing Email Hello Mikel Yup looks good. === Inspecting a header: You can then inspect your added header by doing: email['reply-to'] # => #<TMail::AddressHeader "My Email Address <my_address@anotherplace.com>"> If you just want to the actual value, not the AddressHeader object, pass to_s to this. email['reply-to'].to_s # => "My Email Address <my_address@anotherplace.com>" === Deleting a header: One way of deleting a header from an Email is just assigning it nil like so: email['reply-to'] = nil # => nil If you now puts the email again, it will not be included: puts email Return-Path: <mikel@nowhere.com> Date: Sun, 21 Oct 2007 19:38:13 +1000 From: Mikel Lindsaar <mikel@nowhere.com> To: mikel@somewhere.com Message-Id: <009601c813c6$19df3510$0437d30a@mikel091a> Subject: Testing Email Hello Mikel === Writing out an Email: You can just call to_s on any email to have it serialized out as a single string with the right number of line breaks and encodings. == CONTRIBUTING: You can visit the {Contributing to TMail}[link:http://tmail.rubyforge.org/contributing/] to find out how to contribute to TMail, developers are welcome and wanted! == REQUIREMENTS: * C compiler if you want the Ruby extension for Scanner * Ruby 1.8 or later == INSTALLATION: * sudo gem install tmail Or manually, * sudo script/setup == LICENSE: (The MIT License) Copyright (c) 2007 FIX Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
No description provided.
No description provided.
No description provided.