- How do I install juststeveking/resume-php with Composer?
- Install it with Composer by requiring juststeveking/resume-php and pinning the constraint to ^1.0 so you stay on the current, reworked API. The package is MIT-licensed and framework-agnostic, so it works in plain PHP projects as well as Laravel applications. There is no service provider or config publishing step described, so installation is essentially a single Composer command. Check the 1.0.x tag and CI status before you commit the lockfile.
- Does resume-php work with Laravel 11 and PHP 8.2?
- The package follows Laravel-ecosystem conventions but a supported PHP and Laravel version matrix is not explicitly guaranteed in the available documentation. It most likely requires a modern PHP runtime such as 8.2 or newer and a current Laravel release. Confirm the actual constraints in the package composer.json and verify CI is green on the 1.0.0 tag before you commit. If your service runs an older runtime, treat that as a pre-condition to resolve, not a detail.
- Is resume-php 1.0.0 a breaking change from 0.0.2?
- Yes, treat 1.0.0 as a different API from 0.0.2. The release notes describe major fixes and improvements to how resumes are built, which means the construction code was reworked and any prototype written against 0.0.2 is stale. Re-run your spike on 1.0.x and report estimates as a range until you have. Look for a dedicated upgrade note rather than relying on PR titles alone.
- What is the AI skill mentioned in the resume-php 1.0.0 release?
- It is ambiguous from the release metadata whether it is shipped runtime code, a CLI, or a repository artefact only. Verify this concretely in the source before adopting the package, because a previously pure data path may have gained outbound network calls or non-determinism. If it does execute at runtime, it should be opt-in and disabled by default. Treat that verification as a blocking task for the engineer integrating the package.
- Can resume-php export my resume as JSON Resume compatible data?
- Yes, the package models your CV as structured data and exports a structured JSON resume that targets the JSON Resume schema. That schema is a known public contract rather than a vendor-specific format, which keeps your resume portable. Section coverage includes basics, work history, education, skills, projects, and custom sections. It does not handle styled rendering or ATS scoring, so those remain separate concerns.
- Does juststeveking/resume-php generate PDF or DOCX files?
- No. The package owns resume as data only and explicitly does not handle PDF or DOCX parsing, styled or PDF rendering, ATS scoring, or match ranking. Those are separate workstreams with their own cost and risk. In practice you export the JSON and hand it to your own renderer, which is where most of the effort lives. Do not assume adopting this package de-risks the full resume capability.
- Is work location optional in resume-php 1.0.0 and what happens if I leave it out?
- Version 1.0.0 added structured work location to work entries, but you should verify whether the field is nullable and whether output degrades gracefully when absent. Test the omitted-location case explicitly and add a golden file for it. If you persist resume data, remember that adding a field like location becomes a data migration, so decide the persistence boundary before the first production write. Keeping the field optional at the boundary protects you from churn in the schema.
- How do I write tests for a resume built with resume-php?
- Test the exported data rather than the internal builder calls, so refactors inside the package do not break your suite. Golden-file or snapshot tests on the JSON output are the practical approach, but confirm the output is deterministic first, since embedded timestamps or unstable ordering make golden files brittle. There are no upstream tests you can lean on, so these tests are yours to own. Pair them with a thin adapter interface so vendor type changes surface in one place.
- Who maintains resume-php and how risky is it to depend on?
- It appears to be a single-maintainer package with no meaningful adoption in the wild, so the bus factor is effectively one. It is still a reasonable dependency because a resume data model is a leaf concern in a document-production layer and can be replaced in weeks if it stalls. Wrap the vendor types behind your own ResumeBuilder or ResumeRenderer interface so substitution stays a contained task with a small estimate. Pin the lockfile and keep a documented fork-and-patch contingency.
- What are good alternatives to resume-php for building a CV as code?
- The lowest-risk alternative is modelling the resume in your own typed classes and serialising to the JSON Resume schema, since the schema is public and stable. General-purpose JSON Resume tooling in other languages can also render the same output if you only need the data layer in PHP. Another option is a YAML or Markdown source with a custom exporter, which trades fluent PHP APIs for simpler authoring. If you want typed construction without owning it, resume-php is cheap to adopt behind an adapter, which makes switching later straightforward.