Issue #2044💬 AnsweredOpened May 29, 2019by eduardonunesp1 reactions

Npm start to develop on local server didn't work

Quick answerby artf1

I made a quick check and the reason seems to be the latest [email protected] I don't have time to investigate so I'll just freeze the currently used version

Read full answer below ↓

Question

Did the procedure to start the local server using dev branch as described on README, it worked on the console, but fails on chrome and the grapesjs don't load due to the following error

image

Answers (3)

artfJune 19, 2019

I made a quick check and the reason seems to be the latest [email protected] I don't have time to investigate so I'll just freeze the currently used version

artfMay 30, 2019

Weird, never seen that before. It might be some dev dependency change in some minor release. Try to reinstall node_modules with exact dependency versions

verdvermJune 3, 2019

I'm having issues following the dev setup: Maybe a bundler issue? I am able to drop the min from grapes.min.js in the index.html file and it works. However, if I build the grapes.js output, then this error returns.

Related Questions and Answers

Continue research with similar issue discussions.

Paid Plugins That Match This Issue

Curated by issue keywords and label relevance to help you ship faster.

View all plugins

Loading paid plugin recommendations...

Free option

Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.

Browse free plugins →
Premium option

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.

All tutorials →

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.