You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi - I have a short suggestion for adding to the docs! This was something I struggled with a bunch.
For the main usage documentation, add one line:
import { FormeoEditor, FormeoRenderer } from 'formeo' // you have this
import "formeo/dist/formeo.min.css" // this is missing
(I'm adding this as an issue because I'm not super familiar with different packaging systems in javascript. This was required in webpacker with Rails 6.0.2.2.)
The README's usage section has included import 'formeo/dist/formeo.min.css' since v4.1.2, and the package exports map exposes that path, so webpacker, Vite and friends resolve it. The editor also tries to load the stylesheet from a CDN by default (the style option), but importing it yourself is more reliable, and a page that only uses FormeoRenderer needs the import because the renderer doesn't load any CSS. Closing this.
Activity
shaunakv1 commentedon Sep 24, 2020
I can vouch for this. Form editor renders wonky in rails without importing the css. Def needs to be part of the documentation.
BintLopez commentedon Nov 19, 2020
+1 to this
kevinchappell commentedon Sep 25, 2026
The README's usage section has included
import 'formeo/dist/formeo.min.css'since v4.1.2, and the packageexportsmap exposes that path, so webpacker, Vite and friends resolve it. The editor also tries to load the stylesheet from a CDN by default (thestyleoption), but importing it yourself is more reliable, and a page that only usesFormeoRendererneeds the import because the renderer doesn't load any CSS. Closing this.