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

@joblist/job-board-providers

v0.1.0

Published

job board providers elements

Downloads

4

Readme

This project is now unmaintained, and deprecated in favor of @joblist/components with which it has been merged. See the documentation for the job-board web-component.

job-board-providers (deprecated/unmaintained)

web-components (browser) and node modules to communicate with job-board providers APIs, and list the jobs of companies.

Installation

npm add --save @joblist/job-board-providers

Usage in browser

You will need to import the script in your code, with one of these import:

<script type="module" src="./src/index.js"></script>

web-components

A few convenience web components are defined.

<job-list
	provider-name="greenhouse"
	provider-hostname="gnosis"
></job-list>
<job-list-greenhouse hostname=""></job-list-greenhouse>
<job-list-personio hostname=""></job-list-personio>
<job-list-recruitee hostname=""></job-list-recruitee>
<job-list-smartrecruiters hostname=""></job-list-smartrecruiters>

For the full list of supported providers, check out the ./src/apis folder, where all the known and supported providers are listed.

Open an issue on this repository if there is any bug, and to request/implement new job board providers.

Usage in node

This repo has no build dependency, is developed browser first, and does not provide polyfills for certain browser methods.

You can create the utility files and import in your global /index.js file (or where you need it).

Global dependency for all providers

  • install: npm install --save node-fetch
  • then import './utils/fetch-polyfill.js
// ./fetch-polyfill.js
import fetch from 'node-fetch'

/* make fetch available globally */
if (!globalThis.fetch) {
	globalThis.fetch = fetch
}

export default {}

Dependency for the personio provider:

  • install: npm install --save jsdom
  • then import './utils/domparser-polyfill.js'
import jsdom  from 'jsdom'
const { JSDOM } = jsdom

/* make DOMParser available globally */
global.DOMParser = new JSDOM().window.DOMParser

Development

To run a local development server:

  • npm install, run once to install development dependencies
  • npm run develop, to run the local development server

To see your changes, refresh the browser tab, or restart the development server.

Build for production

There is not build step, no minification, the project is deployed as is.

Deployment to production

To deploy a new version to npm, create a new git tag ex v0.0.1 (needed vXX.XX.XX pattern).

It should be the same as the tag on package.json.version, and this will run the publish to npm job in ./gitlab-ci.yml.

The NPM_TOKEN is defined at the organisation level.

Note that the variable is available only:

  • on protected branch main
  • on protected tag v*