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

overseas-working-visitors

v0.1.0

Published

Overseas Working Visitors Landing Page

Downloads

1

Readme

Overseas Workers Build status code style: prettier style: styled-components EMA for Overseas Working Visitors

Overseas Working Visitors Landing Page

Related Links.
https://www.nib.com.au/overseas-working-visitors
https://www.nib.com.au/overseas-working-visitors/482-temporary-skills-shortage-health-insurance
https://www.nib.com.au/overseas-working-visitors/457-visa-health-insurance
https://www.nib.com.au/overseas-working-visitors/485-temporary-graduate-visa-health-insurance

Make sure that you have the Gatsby CLI program installed:

Last worked with node 14.19.1,

** note deleting package-lock.json file will cause build errors

npm install --global gatsby-cli

Then you can run it by:

npm install
npm run develop

And proceed to http://localhost:8000/

Production build

To see a preview of the production build, simply run:

npm run build
npm run serve

And proceed to http://localhost:9000/

Note: Due to the path-prefix, assets (client side JS, images, fonts) will likely not load locally. The same behaviour is experienced in kaos when accesses the static site directly from s3. To see a working site you must also configure the location in the nib-www-router. or you can try running

To run through the www router locally

Get the latest version of the www router (which points to http://localhost:9000) Run the docker box via vagrant or on your host machine


gatsby build --prefix-paths
gatsby serve -H 0.0.0.0

Testing in Kaos

slice-of-overseas-working-visitors = BRANCH_NAME

Features

Steve for publishing

The starter has a familiar /deploy directory with an apps.yml and Gemfile for steve pipeline management.

Prepush hook

There is a prepush hook that formats your code with prettier and runs unit tests.

Styled Components for styling

Hot module reloading

Jest for unit testing

Prettier for code formatting

React-html for a common html layout and third party scripts

Our Theme component to provide styling information and css normalize

Commonly used nib design system components

Logs

Chat launcher local development

There's a environment variable flag that you can set for local development convenience when it comes to testing and debugging the @nib/chatbot-launcher package (which is centralised in the <Layout/> component. Note that this only affects behaviour in localhost.

#.env.development

# If you're running the `client` locally, in the `chatbot-client-monorepo`:
REACT_APP_LOCAL_CHAT_LAUNCHER_URL=http://localhost:8080

Note that this overrides the URL protocol, origin, AND path. As such you shouldn't expect the prop suffix path to be added to this URL. If you want to test different path suffixes, then you'll need to include that in your env var value.

Note, however, that any calculated query parameters (e.g. load external config) ARE appended to the local override URL as well.