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

@firstclasspostcodes/svelte

v2.3.1

Published

Firstclasspostcodes component library for the Svelte framework

Downloads

6

Readme

Firstclasspostcodes

Build, test and release Cypress Dashboard

We've designed our Svelte component library to be as flexible as possible enabling you to quickly configure build or enhance any form with postcode lookup.

Note: This libary is also used to power our drop-in browser plugin. The documentation provided inside README.md is for the plugin and the documentation displayed on GitHub.

Documentation

See @firstclasspostcodes/svelte for detailed usage, guides and examples.

Installation

Install the package with:

npm install @firstclasspostcodes/svelte -s

Once installed, import the component inside a component file:

<script>
	import PostcodeLookup from '@firstclasspostcodes/svelte';
</script>
<main>
  <PostcodeLookup apiKey="111111111111" />
  <form>
    <div>
			<label for="postcode">Postcode</label>
			<input name="postcode" type="text" data-address-postcode />
		</div>
  </form>
</main>

For more guides and information on how to configure and use the components, read our documentation.

Development

Because Svelte is highly portable (and awesome), the library is primarily used to power our drop-in browser plugin. The fact that the <PostcodeLookup/> component can be exported to provide a Svelte library, is a happy side-effect.

Any development on this library must be portable, or avoid adversely affecting usage inside the browser plugin; enabling continued support of IE11 with Polyfills.

The guiding principle for developing this library is KISS (keep-it-simple-stupid). If you're developing something that seems undocumented or off the paved road, you're probably doing something wrong. It is always best to open an issue to discuss it first.

Getting started

Run the mock API container, this will provide some data you can develop & test with locally:

docker run --rm -d -p 2345:80 firstclasspostcodes/mock:latest

For development, we use index.html, which is served by the parcel bundler. The intention of this webpage, is to provide some visual feedback for the library and allows for experimental usage. Most importantly, it is the page used by Cypress for integration testing.

Start the development app:

npm start

Open your browser and point it at the URL displayed in the terminal. The browser plugin will not automatically start. Open the developer tools and run the following:

window.initPlugin();

Testing

All changes to modules should be accompanied with matching tests and functional changes should have accompanying integration tests, written using Cypress.

Run the tests:

npm test && npm run lint

Cypress

Provide necessary Cypress variables to run the testing suite:

Headless:

CYPRESS_API_URL=http://localhost:2345 CYPRESS_API_KEY=111111111111 npm run cypress

Interactively:

CYPRESS_API_URL=http://localhost:2345 CYPRESS_API_KEY=111111111111 npx cypress open