Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@dfds-platform/business-components

Package Overview
Dependencies
Maintainers
3
Versions
1052
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@dfds-platform/business-components

Shared react components within DFDS

  • 15.0.1
  • latest
  • npm
  • Socket score

Version published
Weekly downloads
482
increased by125.23%
Maintainers
3
Weekly downloads
 
Created
Source

@dfds-platform/business-components-ts

Installation

Install with npm:

npm install --save @dfds-platform/business-components-ts

Install with yarn:

yarn add @dfds-platform/business-components-ts

Environment

For development you need to create a .env file with they following keys.

key
AUTH_ISSUER
AUTH_CLIENT_ID
CONTENTFUL_SPACE_ID
CONTENTFUL_TOKEN
CONTENTFUL_ENVIRONMENT

Look in .env.development for default values.

Publishing

New releases are created in github which will create a new tag. ADO will pick up on the new tag and publish a version with the that tag using the ci:publish npm script

Login component and AuthProvider configuration example:

Go to example

It can be handy to use developing functionality in the context of an existing app. yarn link can be used in that case.

Getting started

A common problem when using yarn link is that you end of with multiple versions of packages (eg. react). This is because dependencies are resolved upwards from within the symlinked react-components folder.

webpack

If you are using webpack you can try setting resolve.symlinks to false in your webpack.config.js to only resolve dependencies from the apps node_modules folder.

Gatsby

Gatsby uses webpack under the hood, so in order to set resolve.symlinks add the following to the gatsby-node.js file

exports.onCreateWebpackConfig = ({ getConfig, actions, stage }) => {
  const config = getConfig()
  config.resolve.symlinks = false
  actions.replaceWebpackConfig(config)
}

Browser compatibility / polyfill

The auth components use the okta-auth-js library behind the scenes. Compatibility with IE 11 / Edge can be accomplished by adding polyfill/shims for the following objects:

  • ES Promise
  • Array.from
  • TextEncoder
  • Object.assign
  • UInt8 typed array
  • webcrypto (crypto.subtle)

Okta auth js git repository

Example usage with gatsby:

import 'core-js/es/promise'
import 'core-js/es/typed-array/uint8-array'
import 'core-js/features/array/from'
import 'core-js/web/url'
import 'webcrypto-shim'
if (typeof window !== 'undefined' && typeof window.TextEncoder !== 'function') {
  const TextEncodingPolyfill = require('text-encoding')
  window.TextEncoder = TextEncodingPolyfill.TextEncoder
  window.TextDecoder = TextEncodingPolyfill.TextDecoder
}

FAQs

Package last updated on 12 May 2023

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