- How do I install dinandmentink/nova-markdown in a Laravel Nova project?
- Install it with Composer using composer require dinandmentink/nova-markdown, then register the field class in your Nova resource. Check the package composer.json constraints against your installed laravel/nova version before requiring it. If the package ships a prebuilt dist asset pair, publish or register those assets according to its README.
- Does dinandmentink/nova-markdown support Laravel Nova 4?
- It is unlikely to support Nova 4 without a fork. The package is archived and appears to target Nova 3.x and below, while Nova 4 changed the field compilation toolchain. Treat Nova 4+ as a hard incompatibility unless you verify a prebuilt dist and successfully test the field in your Nova version.
- How does nova-markdown store Markdown content in the database?
- It stores Markdown as plain text in a normal text or mediumText column through Eloquent. There is no proprietary serialization, no side table, and no write path outside your model. That makes the field replaceable later without a data migration.
- Does nova-markdown render Markdown to HTML for the front end or API?
- No. The package handles authoring only, not published output. Rendering, sanitization, caching, and front-end presentation remain your application's responsibility. Use league/commonmark or Laravel's Str::markdown() plus an HTML sanitizer for display.
- Is it safe to display Markdown authored with nova-markdown without sanitizing the HTML?
- No, you should not assume the rendered output is safe. The editor preview may render raw HTML, and the package does not own the render contract. Sanitize server-side HTML output and test XSS payloads before non-technical editors use the field.
- What Laravel and PHP versions does nova-markdown support?
- Support depends on the package composer.json constraints, which may pin illuminate/support versions that block Laravel 10 or 11 upgrades. Old Nova field packages are a common silent blocker during platform upgrades. Verify dependency resolution in a spike before committing to the package.
- Do I need to compile JavaScript assets to use nova-markdown?
- Only if the package does not commit a prebuilt dist directory. If prebuilt JS and CSS assets are included, integration can work without touching your front-end toolchain on an older Nova. If it requires npm run prod against Nova's Mix or Vite setup, treat Nova 4+ as incompatible.
- What are alternatives to nova-markdown for Markdown editing in Nova?
- A plain Nova Textarea with a preview tab plus server-side rendering via Str::markdown() or league/commonmark often satisfies editors. You can also build a small custom field or choose a maintained Markdown field package that supports your Nova version. The cheaper answer is usually textarea plus sanitized server-side render.
- How should I test nova-markdown in a Laravel application?
- Test that the field persists plain text correctly in your model and column. Add tests for sanitized rendered output, including common XSS payloads, and verify Composer dependency resolution against your target Nova and Laravel versions. Also test asset publishing in a staging Nova panel before rollout.
- Is dinandmentink/nova-markdown actively maintained?
- No, the upstream repository is archived and receives no security or compatibility patches. It has a bus factor of one and no meaningful community fallback. For a Nova 3 or lower estate, fork and vendor it as an owned component rather than relying on it as a straight Composer dependency.