BUGS:Documentation/Clarity
If grapejs requires NodeJS, the doc/wiki should say that clearly upfront somewhere Indeed it doesn't... you need nodejs just for the development purposeYou mention it runs in a CMS, but don't state that it will create a full page and can or cannot run outside of a CMS I think you should read better that statement...Qu...
Read full answer below ↓Question
If grapejs requires NodeJS, the doc/wiki should say that clearly upfront somewhere (i.e. list major dependencies and what type of server is needed to run it). You mention it runs in a CMS, but don't state that it will create a full page and can or cannot run outside of a CMS.
Question: If it runs with NodeJS - will it run on AWS Lambda (serverless)?
Thanks Neal
Answers (3)
If grapejs requires NodeJS, the doc/wiki should say that clearly upfront somewhere
Indeed it doesn't... you need nodejs just for the development purpose
You mention it runs in a CMS, but don't state that it will create a full page and can or cannot run outside of a CMS
I think you should read better that statement...
Question: If it runs with NodeJS - will it run on AWS Lambda (serverless)?
Sure
Thanks Art.
Okay - let's re-read this: "GrapesJS was designed to be used inside a CMS to speed up the creation of dynamic templates."
That could mean I need a CMS then I paste GrapeJS into it; or it could mean it was meant for a person to create his or her own CMS.
Maybe you could just add that "; and it always works fine to build independent HTML pages.
Now back to NodeJS - so there are Node-JS libraries you use that are needed to design/develop a page; but when I deploy to a server, they are not needed? Just the two lines on the getting started page:
<link rel="stylesheet" href="path/to/grapes.min.css"> <script src="path/to/grapes.min.js"></script>This isn't for work; but I'm new on my current job; and everybody assumes I know what they know - so they get tired of my basic questions. :)
Yeah it's not only about CMS but a general purpose use. Inside grapes.min.js you will get everything you need, NodeJS is just for a correct development server (testing, merging dependencies, etc..)
Related Questions and Answers
Continue research with similar issue discussions.
Issue #963
[Question] Create PHP endopoint to remote Storage Manager
Hello. I'm integrating GrapeJS with PHP (CodeIgniter) and I saw that there are others who do this. But I looked in the documentation and ch...
Issue #943
[BUG]: Checkbox trait doesn't remove attribute when unchecked
When html attributes are true or false, the should either exist or not exist. For example, required. This don't have a value in HTML5. Vali...
Issue #1965
Custom content type
@artf Instead of using plugins js files, can we create our own content using html as I have done below. Is it a correct way to do it? Sorry...
Issue #1881
Commands with a stop method, never programmatically stoped don`t run again!
Problem When you add a custom command with stop and dont stop will not run again if I dont set force: 1 as a parameter when running. When y...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.
Browse free plugins →Premium plugins ship with support, regular updates, and production-ready features — save days of integration work.
Browse premium plugins →Related tutorials
In-depth guides on the same topic.
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.