- Is ns/simplemde-bundle a Laravel package?
- No. ns/simplemde-bundle is a Symfony bundle that wraps the SimpleMDE JavaScript editor using Symfony bundle, DI, Twig form theme, and Form type conventions. It does not ship a Laravel service provider, Blade views, or Laravel validation integration, so it will not work as a drop-in Laravel dependency. For Laravel, treat it as a reference implementation and build a small Blade component plus a Vite-loaded editor instead.
- How do I install ns/simplemde-bundle in a Laravel app?
- You should not install it as a Laravel dependency. Composer may resolve it, but it brings Symfony-oriented code and provides no Laravel auto-discovery, service provider, or Blade assets. The practical path is to install EasyMDE from npm, import it through Vite, and initialize it on a textarea inside a Blade component.
- Which Laravel versions does ns/simplemde-bundle support?
- None are declared or supported because the package targets Symfony, not Laravel. There is no Laravel service provider, config file, Blade directive, or form integration to version against Laravel releases. Check its composer.json for Symfony and PHP constraints only if you are evaluating it for a Symfony project.
- Can I use SimpleMDE in a Laravel Blade form?
- Yes, but integrate the editor directly rather than through this bundle. Add easymde via npm, import its JS and CSS in your Vite entry point, and initialize it against a textarea rendered by a Blade component. Keep a plain textarea fallback and validate the submitted markdown on the server.
- Is SimpleMDE still maintained?
- SimpleMDE is effectively unmaintained, and EasyMDE is the community successor. Bundling the archived editor creates browser-compatibility and potential security liability over time. For new Laravel work, use EasyMDE or another actively maintained editor.
- How do I replace SimpleMDE with EasyMDE in Laravel?
- Install easymde with npm, import its JavaScript and CSS through Vite, and initialize it on a textarea in your Blade or Alpine component. Configure the toolbar and preview options in the initializer, and mirror the same field name so validation stays unchanged. If you render stored markdown, sanitize the resulting HTML server-side.
- Does ns/simplemde-bundle sanitize markdown output?
- The bundle is an editor and form-widget wrapper, not a server-side markdown renderer, so do not assume it sanitizes output. Any HTML produced from stored markdown must be sanitized before display. In Laravel, pair a markdown renderer such as league/commonmark with an HTML purifier or a strict allowlist.
- What are the best alternatives to ns/simplemde-bundle for Laravel?
- The most direct alternative is EasyMDE loaded through npm and Vite and wrapped in a Blade, Livewire, or Alpine component. You can also use any maintained Laravel markdown editor package, but verify its maintenance and asset pipeline. For rendering, use league/commonmark plus a sanitizer rather than relying on an editor bundle.
- Is ns/simplemde-bundle safe for production?
- It carries high relative risk: the upstream SimpleMDE editor is unmaintained, the bundle has a single maintainer, one star, no dependents, and no visible CI. Its asset publishing approach may also conflict with modern Vite or Encore pipelines. If you adopt it on Symfony, spike it, check version constraints, and plan to fork; for Laravel, skip it.
- How do I test markdown editor integration in Laravel?
- Write a feature test that the form renders the textarea and accepts submitted markdown, and assert validation rules on the field. Use Laravel Dusk or a browser test if you need to confirm the JavaScript editor initializes and syncs its value. Also test that rendered markdown is sanitized before it is shown.