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

@highpoint/compile-branding

v3.0.0

Published

Utility to compile HighPoint application branding

Downloads

5

Readme

Compile Branding

Utility to compile HighPoint application branding.

Installation

yarn add -D @highpoint/compile-branding

Usage

Copy .env-sample to your application's root directory and name it .env. Populate the values. You can reference the table below for examples of what values should be used. This file should not be included in your source control, so add it to your .gitignore (or similar) file.

Environment Variables

| Variable | Example | | -------------- | ------------------------ | | PS_HOSTNAME | cs92-devo.mhighpoint.com | | PS_ENVIRONMENT | csdev92 | | PS_NODE | SA | | PS_USERNAME | PS | | PS_PASSWORD | mysupersecretpassword | | HTTP_USERNAME | PS | | HTTP_PASSWORD | mysupersecretpassword |

API

compileBranding

Produces a compiled version of the branding in a local directory.

Example

const { compileBranding } = require('@highpoint/compile-branding');
const { resolve } = require('path');

compileBranding({
  app: 'app',
  inFile: resolve(`./src/main.scss`),
  outDir: resolve('./dist'),
  weblib: 'WEBLIB_H_BRNDNG'
}).catch(({ message }) => console.error(message));

Variables

app

The abbreviation of the application whose branding is being compiled.

Examples: app, dp, mc, sb

inFile

The absolute path to the SCSS file that acts as the template for compiling branding.

Example: path.resolve('./scss/main.scss')

outDir

The absolute path to the directory that the compiled CSS files should be outputted to.

Example: path.resolve('./dist')

weblib

The PeopleSoft web library that will be called. It needs to have the following functions:

  • IScript_GetVars
  • IScript_CompileTemplate

Example: WEBLIB_H_BRNDNG

triggerCompile

Triggers branding compilation remotely. This is primarily used by continuous integration services (e.g. Jenkins) to tell PeopleSoft that it should compile the branding.

Example

const { triggerCompile } = require('@highpoint/compile-branding');

triggerCompile({ weblib: 'WEBLIB_H_BRNDNG' }).catch(({ message }) => {
  console.error(message);
  process.exit(1);
});

Variables

weblib

The PeopleSoft web library that will be called. It needs to have the following function:

  • IScript_Compile