Issue #1453πŸ’¬ AnsweredOpened Sep 22, 2018by DanielRuf0 reactions

Big repository size

Quick answerby artf

Hi Daniel, to be honest, I never looked at the size of the repo so thanks for the report. I can run git gc --aggressive --prune=now but it's not that effective (-15% in size). Unfortunately, skipping dist files is not an option because this is what you actually use when you call import grapesjs from 'grapesjs' I close...

Read full answer below ↓

Question

Currently the repository is 40 MB big. It looks like built / dist files and dev files are tracked and not ignored. List of deleted files:

Answers (3)

artfβ€’ Sep 29, 2018

Hi Daniel, to be honest, I never looked at the size of the repo so thanks for the report. I can run git gc --aggressive --prune=now but it's not that effective (-15% in size). Unfortunately, skipping dist files is not an option because this is what you actually use when you call import grapesjs fro...

DanielRufβ€’ Sep 29, 2018

because this is what you actually use when you call import grapesjs from 'grapesjs'

Which should be generally just published with npm publish and be in .gitignore in the ideal case ;-)

lock[bot]β€’ Sep 29, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

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.