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

simpler-mapper

v1.0.0-alpha003

Published

A javascript, profile-based model mapping library.

Downloads

5

Readme

npm version Build Status dependencies Status devDependencies Status codecov Greenkeeper badge

Simpler Mapper

A recursive, object-to-object mapper with optional mapping profiles.

  • For straight name-for-name mapping, no profile is needed.
  • Use a profile for:
    • specifying different source or destination names,
    • value transformations,
    • beforeMap or afterMap callbacks.

Usage

Basic usage with a mapping profile:

import { Mapper } from 'simpler-mapper';

// assumes class Accountant { ... } exists:
let mappingProfile = { exceptions: { homePhone: "cellPhone", fullname: p => p.First + " " + p.Last } };
let mapper = new Mapper();
let accountant = mapper.map(person, Accountant, mappingProfile);

Or, you can implement the MapperProfile<TSource, TDest> interface to improve maintainability:

class MyProfile implements MapperProfile<Person, Accountant> {
    exceptions = {
        homePhone: "cellPhone" as keyof Person,
        fullName: (p: Person) => p.First + " " + p.Last
    };

    beforeMap(src: Person): Accountant {
        const a = new Accountant(src);
        // ...super custom stuff...
        return a;
    }
}
let mappingProfile = new MyProfile();

In fact, a project can have many such mapping profiles, and they can inherit from (or be composed of) each other to ease your workload.

Beyond lambdas and property name overrides, you can also specify beforeMap and afterMap callbacks:

let mapper = new Mapper();
let mappingProfile = { afterMap: (src, dest, p) => dest["key"] = "val" };
let accountant = mapper.map(person, Accountant, mappingProfile);

That's about it. Personally, this is all I've needed. Just how much simpler is Simpler Mapper? It's one class, and its supporting interfaces, and type definitions.

Installation

npm install --save-dev simpler-mapper

History

Q: Didn't you already make a mapper?

A: Yes, but it wasn't simple/effective enough. It relied on annotations and wasn't very flexible.