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
The dist folder is getting pretty large, especially since the output of the TypeScript compilation process is being put there. The original reason for including this folder was to provide an easy way for users to download minified browser bundles. We should stop checking in this folder to the repo and address that issue in a better way.
Scope
The proposal is:
Delete the dist folder from the repo and put it in the .gitignore (and maybe also .dockerignore 🤔).
For each GitHub release we have, retroactively generate bundles (or steal from previous versions in the repo history) and upload them as release assets.
Update our readme to direct users toward the GH release page to download minified browser bundles.
Create a new file to document the publishing process. This should include:
The commands needed to fully populate the dist folder before publishing (i.e. how to generate bundles and types from source).
Directions about which files need to be uploaded to new GH releases. Future releases should use CDNs, so maybe we can include a link to a CDN in the GH release?
Summary
The
dist
folder is getting pretty large, especially since the output of the TypeScript compilation process is being put there. The original reason for including this folder was to provide an easy way for users to download minified browser bundles. We should stop checking in this folder to the repo and address that issue in a better way.Scope
The proposal is:
dist
folder from the repo and put it in the.gitignore
(and maybe also.dockerignore
🤔).dist
folder before publishing (i.e. how to generate bundles and types from source).Directions about which files need to be uploaded to new GH releases.Future releases should use CDNs, so maybe we can include a link to a CDN in the GH release?Urgency
This blocks #323.
The text was updated successfully, but these errors were encountered: