Skip to content
yutils
Example

Options

Fields: id(int), name(string), email(email), joinedAt(date)
Count: 2

Output (JSON, 2 rows)

[
  { "id": 1, "name": "Liam", "email": "liam@example.com", "joinedAt": "2025-09-12T08:43:00Z" },
  { "id": 2, "name": "Ada", "email": "ada@example.com", "joinedAt": "2024-11-04T17:21:00Z" }
]

Note

Ids start at 1 and auto-increment. DB export can switch the generated output to SQL INSERT for PostgreSQL, MySQL, or SQLite.

Usage / FAQ

When to use

  • Simulate API responses — generate a JSON array fast
  • Compare empty vs populated states in frontend components
  • Draft DB seed data without hand-crafting rows
  • Create test fixtures with realistic name / email / date values
  • Switch to SQL INSERT for local database import tests

FAQ

Q.How random are the values?
A.Values are generated with the browser crypto API and refreshed on each regeneration. A deterministic seed option is not exposed yet.
Q.Can I generate Korean names or local addresses?
A.The name catalog includes some Korean names, but full localized address generation is not included. For localized fixtures, use a dedicated generator with a locale-specific dataset.
Q.Are fields cross-consistent?
A.The name and email fields share the same generated name inside a record, but broader semantic dependencies between fields are not enforced. For precise test data, use a dedicated generator.
Fun facts

  • Faker (faker.js) was created in 2010 by Marak Squires — a port of Ruby's Faker to JavaScript. It generates realistic placeholder data (names, addresses, emails, countries) one line at a time, and became the standard for seeding test data.

    faker-js — GitHub

  • The January 2022 'Marak incident' — Marak Squires deliberately published versions of his colors.js and faker.js that printed infinite ASCII (`LIBERTY LIBERTY LIBERTY` forever). It was his protest against large companies free-riding on uncompensated open source — and became a symbolic moment for npm supply-chain risk.

    The Verge — colors.js incident

  • After the incident, the community forked faker.js into the new `@faker-js/faker` package, isolating and archiving the original `faker` on npm. It became a textbook case for fork governance under 'a maintainer holds the library hostage' risk.

    fakerjs.dev — Announcement

Related tools

See all in this category →