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

siding-navigator

v1.1.2

Published

SIDING authentication and navigation.

Downloads

9

Readme

SIDING Navigator

npm version dependencies

Wrapper para autenticarse en el SIDING y navegar a través de sus URLs más comunes.

Instalación

  $ npm install -S siding-navigator

Uso

  const logIn = require('siding-navigator');

  logIn(username, password).then(navigator => {
    navigator.index().then(res => {
      // hemos navegado hacia la landing page del SIDING
    });

    navigator.myCourses(2015, 1).then(res => {
      // hemos navegado hacia el listado de los ramos que cursé durante el 2015-1
    });

    navigator.coursesCatalogue(2015, 1).then(res => {
      // hemos navegado hacia el catálogo de ramos del 2015-1
    });

    navigator.courseAnnouncements(7201).then(res => {
      // hemos navegado hacia los anuncios de la sección 1 de Optimización (2015-1)
      // 7201 corresponde al ID del ramo (se puede encontrar en SIDING).
    });

    navigator.courseProgramme(7201).then(res => {
      // hemos navegado hacia el programa de la sección 1 de Optimización (2015-1)
      // 7201 corresponde al ID del ramo (se puede encontrar en SIDING).
    });

    navigator.courseCalendar(7201).then(res => {
      // hemos navegado hacia el calendario de la sección 1 de Optimización (2015-1)
      // 7201 corresponde al ID del ramo (se puede encontrar en SIDING).
    });

    navigator.visit('una-url-válida-del-SIDING').then(res => {
      // hemos navegado hacia una URL válida del SIDING
    });
  });

Contributing

  1. Hacer Fork al repositorio
  2. Crear la branch de la feature (git checkout -b my-new-feature)
  3. Hacer commit a los cambios (git commit -am 'add my feature')
  4. Hacer push a la rama creada (git push origin my-new-feature)
  5. Crear una nueva Pull Request

Nota: Se debe considerar que los tests requieren un usuario y contraseña para funcionar. Para ello se debe contar con las variables de entorno SIDING_USERNAME y SIDING_PASSWORD.