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

@europeana/portal

v1.82.0

Published

Europeana Portal

Downloads

286

Readme

Europeana Collections portal, made with Vue.js + Nuxt.js

Maintainability Rating Reliability Rating Security Rating Coverage

Prerequisites

  1. Node.js version 16, and npm
  2. Contentful CMS account
  3. Redis cache (included as Docker Compose service for development)

Configuration

Configuration options can be set in a .env file (see .env.example) or via ENV variables on your machine.

Some core features such as authentication and editorial content require the relevant configuration options to be specified. In particular, pay attention to the Europeana APIs, Contentful, Redis and oAuth sections in the example .env file.

Build

# start services
docker-compose up

# install package dependencies
npm install

# serve with hot reload at localhost:3000
npm run dev

# build for production and launch server
npm run build
npm start

For detailed explanation on how things work, refer to Nuxt.js docs.

Testing

To run end-to-end tests, you will need Docker Engine and Compose installed and the docker service running.

Run the full test suite with: npm test

Unit tests

npm run test:unit runs all unit tests.

To run unit tests from a single file, append the full path, e.g. npm run test:unit tests/unit/components/PageHeader.spec.js

End-to-end tests

First, create an env file for the app container, copying tests/e2e/docker/app/.env.example to tests/e2e/docker/app/.env and populating with actual API keys.

npm run test:e2e runs all end-to-end feature tests.

To run a single end-to-end test file, append the full path, e.g. npm run test:e2e tests/e2e/features/common/header.feature

If you have modified app files and want to re-run e2e tests, you will need to first rebuild the generated Docker images in the test stack, with npm run test:stack:rebuild

Visual tests

Ensure that you have set a Percy token as PERCY_TOKEN in tests/e2e/docker/nightwatch-visual/.env, then run npm run test:visual.

License

Licensed under the EUPL v1.2.

For full details, see LICENSE.md.