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

ca-jobapply-frontend

v4.0.0

Published

SEEK Job Apply Frontend

Downloads

2

Readme

Job Apply Frontend

Installation

$ git clone [email protected]:SEEK-Jobs/ca-jobapply-frontend.git
$ cd ca-jobapply-frontend
$ npm install

You'll also need to ensure you have dev and stub subdomains setup in your /etc/hosts

127.0.0.1 dev.seek.com.au
127.0.0.1 stub.seek.com.au

Update the GraphQL schema

npm run update-schema

Getting Started

# Run the project locally.
$ npm start

Once the dev-server is running, you can view the project in your browser by visiting http://dev.seek.com.au:5012/job/1/apply

Data Toggles for API Mocks

Using the dev server, you can toggle whether or not API mocks return certain data. For example, once you've run npm start and the browser has opened, add ?resumesEnabled on to the end of the local Job Apply URL. This will return profile resumes for prefill.

Current Data Toggles

Unauthenticated: ?unauthenticated

Resumes: ?resumesEnabled

No most recent role: ?noRole

No privacy level set: ?noPrivacyLevel

Role requirements: http://dev.seek.com.au:5012/job/4/apply

Staged Apply: http://dev.seek.com.au:5012/job/4/apply?resumesEnabled&features=stagedApply

Logging in locally

Registering locally

Building

# Build the application ready for deployment, with output going to ./dist
$ yarn run build

Normally the build step happens on Teamcity, and you will rarely need to run the command shown above. It is handy to do this from time to time, and to familiarise yourself with the layout of the built application, as it can help prevent nasty bugs resulting from incorrect paths and so forth.

Running Cypress tests

# First build the app, the below command will ensure the same data is used during run on the pipeline
$ yarn test:build

# Then run the tests
yarn test:cypress

Running tests

# Run the unit tests
$ yarn run test:unit
# Run the single chrome tests
$ yarn run test:testcafe

Running in docker

Buildkite agent (CI) runs everything in docker. To run locally using the docker image, use the ./docker-run.sh script

./docker-run.sh yarn run lint

This uses

  • AWS account: CandyConnect-Prod
  • Docker image: 564637108174.dkr.ecr.ap-southeast-2.amazonaws.com/ca-jobapply-frontend:latest

To pass environment variables to docker, use a .env file. Use template .env.local.

Contribution Guidelines

Please ensure your code pass the repository Guidelines before sending a pull request, other wise your pull request will fail the testing and will not be merged.

  • Your code must pass all linting rules.
  • Your code must pass all existing unit tests.
  • Your code must pass coverage test.
  • Your code must pass format/prettier.

Monitoring

Datadog: https://app.datadoghq.com/dashboard/559-92v-hgd/connect-job-apply-frontend-ui