New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

dsc-header-footer

Package Overview
Dependencies
Maintainers
1
Versions
1
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

dsc-header-footer

This repository holds the sources to provide the DSC Header/Footer, as well as the Helmet for consumption on 3rd party sites.

  • 1.1.0
  • alpha
  • latest
  • npm
  • Socket score

Version published
Weekly downloads
5
increased by400%
Maintainers
1
Weekly downloads
 
Created
Source

This repository holds the sources to provide the DSC Header/Footer, as well as the Helmet for consumption on 3rd party sites.

Pipeline | Metrics

Build process

We use Rollup for providing a bundled version of Header/Footer and respective the Helmet. To provide these builds two scripts are defined in package.json.

yarn build:headerfooter
yarn build:helmet

Both commands can also be executed in an chained way using yarn build.

On build the relevant components for header/footer/helmet will be extracted out of the @salesforcedevs/dx-components package and then bundled as single JavaScript components.

The output for Header/Footer will be stored in /public/header-footer, and the output for the Helmet in /public/helmet.

For sites that use a REST based set up (Component Library and Metadata Coverage Report) relevant configuration files will be created under public/config.

QA

The helmet is consumed by apps like www.heroku.com, which has a staging app at www-staging.heroku.com (has basic auth: leave user empty, password is "ronin"). Those apps have a HELMET_HOST config var that can be pointed to your review app, making www-staging fetch the helmet from your PR:

heroku config-set HELMET_HOST=https://your-review-app-name.herokuapp.com -a www-staging

Remember to roll back www-staging after the QA process:

heroku rollback -a www-staging

Server setup

  • Assets are currently served from the https://developer.salesforce.com/shared-components URL (e.g: https://developer.salesforce.com/shared-components/helmet/import.js).
  • The developer.salesforce.com domain is served via Fastly, with the shared-components proxying to a Heroku app (e.g: Fastly fetches https://developer.salesforce.com/shared-components/helmet/import.js from https://dsc-header-server-p.herokuapp.com/helmet/import.js)
  • The Heroku app uses the static Heroku buildpack. The configuration is stored in the static.json file that sets HTTP headers for caching and CORS.

Example markup

The folder scripts/src/templates contains two example HTML files that showcase how to integrate the JavaScript files, and the custom elements.

FAQs

Package last updated on 20 Feb 2024

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc