npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, πŸ‘‹, I’m Ryan HefnerΒ  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you πŸ™

Β© 2024 – Pkg Stats / Ryan Hefner

at-lodash

v4.0.0

Published

improve readibility of your code! πŸ˜„ for es6 and coffeescript this is metaprograming used execution context

Downloads

45

Readme

at-lodash

improve readibility of your code! πŸ˜„ for es6 and coffeescript this is metaprograming used execution context

Usage examples

✏️ es6 when at.config.js writen custom config code located in cwd, auto load that

  • at.config.js
const {fp} = this

module.exports = function(){
  //here execution context applied at-lodash's feature 
  //(ex : auto load node module, npm module, lodash module)
  this.double = fp.map(fp.multiply(2))
}
  • index.js
require('at-lodash').call(this)
const {fp} = this

//auto load lazily lodasy module!
this.sum2mul3 = n => this.flow(
  fp.add(2),
  fp.multiply(3)
)(n)
this.map([1,2,3], this.sum2mul3)
// [9,12,15]

//auto load lazily node module! (ex: http)
const server = this.http.createServer((req, res) => res.end())
server.listen(8000)

//if you installed 'moment' npm module, auto load that!
this.moment([2010, 6, 10])
// July 10th

//auto load at.config.js 
this.double([2,4,6])
// [4,8,12] 

//create special execution context included string.prototype extended by string module
this.string(() => {
  'good at-lodash'.humanize()
  // 'Good at lodash'
})

✏️ coffeescript

  • at.config.coffee
module.exports = => 
  #here execution context applied at-lodash's feature 
  #(ex : auto load node module, npm module, lodash module)
  @double = @fp.map fp.multiply(2))
  • index.coffee
require('at-lodash').call @
{fp} = @

# auto load lazily lodasy module!
@sum2mul3 = (n) => @flow(
  fp.add(2),
  fp.multiply(3)
) n
@map [1,2,3], @sum2mul3

# auto load lazily node module! (ex: http)
server = @http.createServer (req, res) => res.end()
server.listen 8000

# if you installed 'moment' npm module, auto load that!
@moment [2010, 6, 10]
# July 10th

# auto load at.config.js 
@double [2,4,6] 
  # [4,8,12] 

//create special execution context included string.prototype extended by string module
@string( => 
  'good at-lodash'.humanize()
  # 'Good at lodash'
)

installation

npm install at-lodash

Features

every module loaded lazily in execution context!

  • import lodash
  • import famouse module
    • underscroe.string
    • highland
    • string
  • create special execution context included string.prototype extended by string module
  • import module in execution context lazily
    • nodejs module
    • installed npm module in package.json
  • load individual setting in at.config.js