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

la-map

v0.5.1

Published

React component for rendering learn-anything maps

Downloads

16

Readme

NPM

LA Map

A React component for Learn Anything maps (or other mindmaps).

Installation

npm install la-map --save

Usage

import { Component } from 'react';
import { render } from 'react-dom';
import LAMap from 'la-map';
import { nodes, resources } from './my-map.json';

class Example extends Component {
  render() {
    return (
      <LAMap
        nodes={this.props.nodes}
        resources={this.props.resources} />
    );
  }
}

render(
  <Example nodes={nodes} resources={resources} />,
  document.getElementById('target')
);

Testing

To test this repository run these commands

git clone https://github.com/learn-anything/la-map
cd la-map
npm install && npm run test

and connect to http://localhost:4000/

Props

| Prop | Type | Default | Description | |-----------------|:-------:|---------|----------------------------------------------------------------------| | nodes | Object | | Object containing IDs of nodes as keys and child nodes as values. | | resources | Object | | Object containing IDs of nodes as keys and child resources as values.|

nodes

Object containing IDs of nodes as keys and child nodes as values.

Note The root node, has parent null, and has only an object as key.

Example

{
  null: {
    "mapID": 1882,
    "text": "front end",
    "nodeID": 7357,
    "parentID": null
  },
  7357: [
    {
      "mapID": 1882,
      "text": "help",
      "nodeID": 7358,
      "parentID": 7357
    },
    {
      "mapID": 1882,
      "text": "basics",
      "nodeID": 7359,
      "parentID": 7357
    }
  ],
  7359: [
    {
      "mapID": 1882,
      "text": "CSS  ️",
      "nodeID": 7389,
      "parentID": 7359
    },
    {
      "mapID": 1882,
      "text": "javascript  ️",
      "nodeID": 7362,
      "parentID": 7359
    },
    {
      "mapID": 1882,
      "text": "HTML  ️",
      "nodeID": 7360,
      "parentID": 7359
    }
  ]
}

This object would render a tree that looks like this:

  front end (#7357)
  ├── help (#7358)
  └── basics (#7359)
      ├── CSS (#7389)
      ├── javascript (#7362)
      └── HTML (#7360)

The possible attributes for each node are:

  • mapID: ID of the map containing this node
  • text: title of the node
  • nodeID: ID of this node
  • parentID: ID of the parent node

resources

Object containing IDs of nodes as keys and child resources as values.

Example

{
  null: {
    "mapID": 1882,
    "text": "front end",
    "nodeID": 7357,
    "parentID": null
  },
  7357: [
    {
      "mapID": 1882,
      "text": "help",
      "nodeID": 7358,
      "parentID": 7357
    },
    {
      "mapID": 1882,
      "text": "basics",
      "nodeID": 7359,
      "parentID": 7357
    }
  ],
  7359: [
    {
      "mapID": 1882,
      "text": "CSS  ️",
      "nodeID": 7389,
      "parentID": 7359
    },
    {
      "mapID": 1882,
      "text": "javascript  ️",
      "nodeID": 7362,
      "parentID": 7359
    },
    {
      "mapID": 1882,
      "text": "HTML  ️",
      "nodeID": 7360,
      "parentID": 7359
    }
  ]
}

This object would render a tree that looks like this:

  front end (#7357)
  ├── help (#7358)
  └── basics (#7359)
      ├── CSS (#7389)
      ├── javascript (#7362)
      └── HTML (#7360)

The possible attributes for each node are:

  • mapID: ID of the map containing this node
  • text: title of the node
  • nodeID: ID of this node
  • parentID: ID of the parent node

Styling

Here's a list of all CSS classes for styling:

  • .mindmap-svg: main svg element containing the map;
  • .mindmap-node: foreignObject element representing a node;
  • .mindmap-node--editable: foreignObject element representing a node in editor mode;
  • .mindmap-subnode-group-text: foreignObject element containing all subnodes of a given node;
  • .mindmap-subnode-text: div element containing a subnode;
  • .mindmap-connection: path element for each connection;
  • .mindmap-emoji: img tag for emoji

Contributing

If you want a new feature added, you find bugs or you want to help making some changes, feel free to open an issue or submit a pull request. Any help would be greatly appreciated :heart: