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 🙏

© 2026 – Pkg Stats / Ryan Hefner

my-app-de-test

v2.0.0

Published

Composant de formulaire d'enregistrement React avec validation

Downloads

343

Readme

Application d'Enregistrement avec API

npm version

Formulaire d'enregistrement utilisant JSONPlaceholder comme API externe. Tests complètement isolés via mocks Jest et Cypress.

Package npm

https://www.npmjs.com/package/my-app-de-test

Utilisation de la librairie

npm install my-app-de-test
import { RegisterPage, validateFormData, validateAll } from 'my-app-de-test';

v2.0.0 : Breaking change — Les validators unitaires (validateEmail, validateNom, etc.) ne sont plus exportés depuis l'entrée principale. Utilisez validateFormData ou validateAll.

Historique des versions

| Version | Type | Description | |---------|-------|----------------------------------------------------------| | 2.0.0 | Major | Suppression des validators unitaires de l'API publique | | 1.1.0 | Minor | Ajout de validateAll retournant { isValid, errors } | | 1.0.1 | Patch | Guard null dans validateFormData | | 1.0.0 | - | Publication initiale de la librairie |

Démarrage

npm start

Ouvre http://localhost:3000

Tests

Jest (tests d'intégration)

npm test

Cas couverts:

  • Succès (200/201): Données valides, message de succès, formulaire vidé
  • Erreur métier (400): Email existe, données invalides
  • Erreur serveur (500): Crash serveur, comportement graceful, réessai
  • Validation: Pas d'appel API si validation échoue

Cypress (tests E2E)

npx cypress open    # Mode interactif
npx cypress run     # Mode headless

Cas couverts:

  • Workflow complet avec succès
  • Erreur 400 avec message spécifique
  • Erreur 500 sans crash
  • Réessai après erreur
  • Validation locale

Architecture

Les appels axios sont mockés dans les tests pour isoler l'application du serveur.

Jest mock:

jest.mock('axios');
axios.post.mockResolvedValueOnce({ data: { id: 1 } });
axios.post.mockRejectedValueOnce(new Error('Email exists'));

Cypress intercept:

cy.intercept('POST', '**/users', { statusCode: 201, body: {...} });

Fichiers clés

  • src/api/userAPI.js - Service API axios
  • src/UsersContext.js - Gestion d'état avec appels API
  • src/pages/RegisterPage.js - Formulaire avec gestion async
  • src/pages/RegisterPage.test.js - Tests Jest (15+ cas)
  • cypress/e2e/navigation.cy.js - Tests Cypress (5 scénarios)

Production

Pour utiliser une API réelle:

// src/api/userAPI.js
const API_URL = 'https://votre-api.com/users';

Les tests continueront à fonctionner avec les mocks.