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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@cortec/elastic

v1.1.4

Published

Elasticsearch module for Cortec

Readme

@cortec/elastic

Module Overview

@cortec/elastic provides integration with Elasticsearch using the official Node.js client. It supports multiple client instances, configurable via your application's configuration files, and allows secure connections with CA certificates.

This module is designed to be used within the Cortec framework, providing a standardized way to manage Elasticsearch connections and clients.


Configuration Options

Where to put config: Place your Elastic config in config/default.yml (or your environment-specific config file).

Schema:

elastic:
  myClient:
    connection:
      user: 'elasticuser' # Username for authentication
      password: 'elasticpass' # Password for authentication
      host: 'localhost' # Hostname or IP of Elasticsearch node
      port: 9200 # Port number (default: 9200)
      caFile: '/path/to/ca.pem' # Optional, path to CA certificate file for SSL
  analytics:
    connection:
      user: 'readonly'
      password: 'readonlypass'
      host: 'analytics.example.com'
      port: 9200

Field-by-field explanation:

  • elastic: Root key for Elastic config.
  • myClient, analytics: Identity/name for each Elasticsearch client (can be any string).
  • connection: Connection options for @elastic/elasticsearch.
    • user: Username for authentication.
    • password: Password for authentication.
    • host: Hostname or IP address of the Elasticsearch node.
    • port: Port number for the node (default: 9200).
    • caFile: Path to CA certificate file for SSL connections (optional).

How config is loaded: The config is loaded automatically by the @cortec/config module and validated at runtime. Access it in code via:

const config = ctx.provide<IConfig>('config');
const elasticConfig = config?.get<any>('elastic');

If config is missing or invalid, an error is thrown at startup.

You may define multiple clients by specifying different keys under elastic.


Example Usage

import { Elastic } from '@cortec/elastic';

// Instantiate the module (usually handled by Cortec context)
const elastic = new Elastic();

// After context is loaded:
const client = elastic.client('myClient');

// Example: Ping the Elasticsearch node
await client.ping();

// Example: Index a document
await client.index({
  index: 'my-index',
  document: { foo: 'bar' },
});

// Example: Search documents
const result = await client.search({
  index: 'my-index',
  query: { match_all: {} },
});
console.log(result.hits.hits);

Notes

  • The module automatically loads configuration and creates clients for each identity defined in your config.
  • If caFile is provided, the client will use the specified CA certificate for SSL connections.
  • All clients are closed automatically when the module is disposed.

See Also