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

@oriun/timenjoy.js

v1.1.2

Published

This README would normally document whatever steps are necessary to get your application up and running.

Downloads

13

Readme

README

This README would normally document whatever steps are necessary to get your application up and running.

Installation

yarn add @oriun/timenjoy.js
# or with npm
npm i @oriun/timenjoy.js

Usage

<html>
    <head>...</head>
    <body>
        ...
        <div id='tnj'>
            <!-- le widget s'insérera ici -->
            Quelque chose à afficher au cas où une erreur empêche le widget de s'afficher.
        </div>
        ...
    </body>
</html>
// Import du package dans un fichier js
import TimenjoyJS from '@oriun/timenjoy.js';

// Objet avec les options de personnalisation
const TNJOptions = {
    type: "PageView",
    app_secret: "[app_secret]",
    city: "Paris",
    distance: "50",
    topevents: "false",
    categories: "SPECTACLE"
}

// Initialisation d'un widget dans un element avec l'id tnj
const TNJwidget = new TimenjoyJS(
    document.querySelector('#tnj'),
    TNJOptions
)

Dans un projet React

L'idéal est d'appeler la fonction une fois par widget, en la plaçant dans un componentDidMount ou un useEffect, puis d'arrêter le widget lorsque le composant est démonté. L'arrêt est facultatif.

Composant en classe

class MonComposant extends React.Component{
    constructor(props){
        ...
        this.tnjwidget = null;
    }
    componentDidMount(){
        ...
        this.tnjwidget = new TimenjoyJS(
            document.querySelector('#tnj'),
            {/*options*/}
        );
    }
    componentWillUnmount(){
        ...
        this.tnjwidget.kill();
    }
    render(){
        return (
            <>
                ...
                <div id="tnj">
                ...
            </>
        )
    }
}

Composant en fonction

const MonComposant = (props) => {
    ...
    useEffect(()=> {
        const tnjwidget = new TimenjoyJS(
            document.querySelector('#tnj'),
            {/*options*/}
        )
        return tnjwidget.kill
    },[])
    return <>
        ...
        <div id="tnj">
        ...
    </>
}

Dans un projet Angular

L'idéal est d'appeler la fonction une fois par widget, en la plaçant dans un ngOnInit, puis d'arrêter le widget lorsque le composant est démonté dans un ngOnDestroy. L'arrêt est facultatif.

Template


<div>
    ...
    <div id='tnj'>
        <!-- le widget s'insérera ici -->
        Quelque chose à afficher au cas où une erreur empêche le widget de s'afficher.
    </div>
    ...
</div>

Component

class MonComposant extends OnInit, OnDestroy {
    tnjwidget = null
    ngOnInit():void {
        ...
        this.tnjwidget = new TimenjoyJS(
            document.querySelector('#tnj'),
            {/*options*/}
        )
    }
    ngOnDestroy():void {
        ...
        this.tnjwidget.kill()
    }
    ...
}

Dans un projet Vue

Vue2

<template>
  <div class="hello">
    <p>
      ...
    </p>
    <div id="tnj-tnj" style='width:80vw;height:500px'>TimenjoyJS renders here</div>
  </div>
</template>

<script>
import TimenjoyJS from "@oriun/timenjoy-js";

let tnjwidget = null;

export default {
  name: "MonComposant",
  mounted: function() {
    console.log('mounted')
    tnjwidget = new TimenjoyJS(
        document.querySelector("#tnj-tnj"),
        {/*options*/}
    )
  },
  unmounted: function(){
    tnjwidget.kill()
  }
};
</script>

Dans un projet svelte

:warning: L'utilisation de la dépendance crypto-js produit une erreur dans svelte, empêchant le lancement du projet. L'utilisation du package devrait ressembler au code ci-dessous :

<main>
	...
	<div id='tnj'></div>
    ...
</main>
<script>
    import TimenjoyJS from "@oriun/timenjoy.js";
	import { onMount, onDestroy  } from "svelte";
	let tnjwidget = null ;
	onMount(() => {
		tnjwidget = new TimenjoyJS(document.querySelector("#tnj"), {
			type: "PageView",
			app_secret: "[app_secret]",
			city: "Nice",
			distance: "50",
			topevents: "false",
			wmark: "true",
			categories: "SPECTACLE",
		});
	});
	onDestroy(()=>{
		tnjwidget.kill()
	});
</script>