@wavo-cloud.auth

Purpose

This library provides a UIShell React component that can be used to lock down any React-based frontend application behind a login screen. Users will need to be authenticated to use it.

The UIShell component also:

• renders a responsive navbar with links (supplied as props)
• handles various authentication states such as showing a warning then the user is correctly signed in, but hasn't verified their email yet.

Other exports in this library:

• Auth, a module used to interact with Auth0 and handle user sessions.
• UserContext, a React context that can be used to access the currently logged-in user's information.

How to use

import { UIShell } from '@wavo-cloud/auth'

const App = () => (
  {/* UIShell must be wrapped with a Router somewhere up the tree */}
  <Router>
    <UIShell
      navbarLinks={[
        { to: '/', name: 'My Dashboards' },
        { to: '/data-sources', name: 'My Data Sources' },
        { to: '/tag-fields', name: 'My Tag Fields' },
        { to: '/campaigns', name: 'My Campaigns' },
      ]}
      rightMenuLinks={[{ to: '/me', name: 'My Profile' }]}
      appName="Marketing Analytics"
      frontendURL="http://localhost:3000"
      onLogoClick={() => console.log('Logo clicked')}
    >
      <div>Content I can only see if I am authenticated</div>
    </UIShell>
  </Router>
);

ReactDOM.render(<App />, document.querySelector('#root'));

Props

| prop | description | default | |----------|----------------------------|----------| | navbarLinks | Links that will show up in the navbar. Left-aligned. | [] | | rightMenuLinks | Links that will show up in the "My Account" dropdown menu | [] | | appName | Application name that will show up under the logo on the left side of the navbar. | None (required) | | frontendURL | URL of the frontend app. Needed for authentication. | None (required) | | onLogoClick | Function that runs when the logo is clicked | _.noop | | logoImgSrc | Image to use as the logo on the left-side of the navbar | https://d6xgplupeuerl.cloudfront.net/logo-white.png | | logoRedirectURL | If defined, link to navigate to when the logo on the left-side of the navbar is clicked. | undefined | | children | JSX/Components to render when the user is authenticated | None (required) |

Accessing user context

import { UserContext } from '@wavo-cloud/auth'

const ComponentWithUser = () => {
  const { user } = useContext(UserContext);
  return <div>{JSON.stringify(user, null, 2)}</div>
};

The user object contains fields such as isWavoUser, email, email_verified, name, nickname, picture, etc.

Using functions from the Auth module

import { Auth } from '@wavo-cloud/auth'

console.log(Auth.isWavoUser())
// Output: true

console.log(Auth.getUser())
// Output: 
// {
//   "https://auth.wavo.me/user_metadata":{
//     "invitesResolved":true
//   },
//   "nickname":"alexandre",
//   "name":"[email protected]",
//   "picture":"https://s.gravatar.com/avatar/cce8401f25ba0eb2da25ed8a952025ea?s=480&r=pg&d=https%3A%2F%2Fcdn.auth0.com%2Favatars%2Fal.png",
//   "updated_at":"2021-04-12T15:04:34.340Z",
//   "email":"[email protected]",
//   "email_verified":true,
//   "iss":"https://auth.wavo.me/",
//   "sub":"auth0|5cb739166964de11ba530567",
//   "aud":"CufY0aiGpfTNM5Jb46ggnjaj71IjjZt4",
//   "iat":1618262289,
//   "exp":1618262409,
//   "at_hash":"tOp9CPMizURJ3eCVBTsRLw",
//   "nonce":"hNs.UQqItM57yxx4A~7CsChdrOvEZ3G1"
// }

TSDX React User Guide

Congrats! You just saved yourself hours of work by bootstrapping this project with TSDX. Let’s get you oriented with what’s here and how to use it.

This TSDX setup is meant for developing React component libraries (not apps!) that can be published to NPM. If you’re looking to build a React-based app, you should use create-react-app, razzle, nextjs, gatsby, or react-static.

If you’re new to TypeScript and React, checkout this handy cheatsheet

Commands

TSDX scaffolds your new library inside /src, and also sets up a Parcel-based playground for it inside /example.

The recommended workflow is to run TSDX in one terminal:

npm start # or yarn start

This builds to /dist and runs the project in watch mode so any edits you save inside src causes a rebuild to /dist.

Then run the example inside another:

cd example
npm i # or yarn to install dependencies
npm start # or yarn start

The default example imports and live reloads whatever is in /dist, so if you are seeing an out of date component, make sure TSDX is running in watch mode like we recommend above. No symlinking required, we use Parcel's aliasing.

To do a one-off build, use npm run build or yarn build.

To run tests, use npm test or yarn test.

Configuration

Code quality is set up for you with prettier, husky, and lint-staged. Adjust the respective fields in package.json accordingly.

Jest

Jest tests are set up to run with npm test or yarn test.

Bundle analysis

Calculates the real cost of your library using size-limit with npm run size and visulize it with npm run analyze.

Setup Files

This is the folder structure we set up for you:

/example
  index.html
  Navbar.js       # test your component here in a demo app
  package.json
  tsconfig.json
/src
  Navbar.js       # EDIT THIS
/test
  blah.test.tsx   # EDIT THIS
.gitignore
package.json
README.md         # EDIT THIS
tsconfig.json

React Testing Library

We do not set up react-testing-library for you yet, we welcome contributions and documentation on this.

Rollup

TSDX uses Rollup as a bundler and generates multiple rollup configs for various module formats and build settings. See Optimizations for details.

TypeScript

tsconfig.json is set up to interpret dom and esnext types, as well as react for jsx. Adjust according to your needs.

Continuous Integration

GitHub Actions

Two actions are added by default:

• main which installs deps w/ cache, lints, tests, and builds on all pushes against a Node and OS matrix
• size which comments cost comparison of your library on every pull request using size-limit

Optimizations

Please see the main tsdx optimizations docs. In particular, know that you can take advantage of development-only optimizations:

// ./types/index.d.ts
declare var __DEV__: boolean;

// inside your code...
if (__DEV__) {
  console.log('foo');
}

You can also choose to install and use invariant and warning functions.

Module Formats

CJS, ESModules, and UMD module formats are supported.

The appropriate paths are configured in package.json and dist/Navbar.js accordingly. Please report if any issues are found.

Deploying the Example Playground

The Playground is just a simple Parcel app, you can deploy it anywhere you would normally deploy that. Here are some guidelines for manually deploying with the Netlify CLI (npm i -g netlify-cli):

cd example # if not already in the example folder
npm run build # builds to dist
netlify deploy # deploy the dist folder

Alternatively, if you already have a git repo connected, you can set up continuous deployment with Netlify:

netlify init
# build command: yarn build && cd example && yarn && yarn build
# directory to deploy: example/dist
# pick yes for netlify.toml

Named Exports

Per Palmer Group guidelines, always use named exports. Code split inside your React app instead of your React library.

Including Styles

There are many ways to ship styles, including with CSS-in-JS. TSDX has no opinion on this, configure how you like.

For vanilla CSS, you can include it at the root directory and add it to the files section in your package.json, so that it can be imported separately by your users and run through their bundler's loader.

Publishing to NPM

We recommend using np.

Usage with Lerna

When creating a new package with TSDX within a project set up with Lerna, you might encounter a Cannot resolve dependency error when trying to run the example project. To fix that you will need to make changes to the package.json file inside the example directory.

The problem is that due to the nature of how dependencies are installed in Lerna projects, the aliases in the example project's package.json might not point to the right place, as those dependencies might have been installed in the root of your Lerna project.

Change the alias to point to where those packages are actually installed. This depends on the directory structure of your Lerna project, so the actual path might be different from the diff below.

   "alias": {
-    "react": "../node_modules/react",
-    "react-dom": "../node_modules/react-dom"
+    "react": "../../../node_modules/react",
+    "react-dom": "../../../node_modules/react-dom"
   },

An alternative to fixing this problem would be to remove aliases altogether and define the dependencies referenced as aliases as dev dependencies instead. However, that might cause other problems.