initial support for exporting builds

[decanTyme]

PR Includes:

• Add jsdom
• Add postbuild script
• Add npm scripts

Summary:

Adds initial support for exporting and compressing builds (#10). The exported files/zip should not require any server to run, which can then be easily shared.

Sidenote: removed run keyword from scripts since it is perfectly fine omitting it and it shortens some otherwise lengthy scripts.

Sample compressed export: export.zip

Instructions/docs:

Run yarn export:optimized to export and compress the build files. The resulting files do not need any servers to run (i.e. you can open it directly in a browser without using a dev server.) The compressed (zip) file will be saved inside dist/. To export without minification and other optimizations, run yarn export. For convenience, there is a yarn compress script that you can use if you do not want the postbuild script to run, which is used to prepare the files for running without a server.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/warengonzaga/css-text-portrait-builder/2m2JDmfjbKKjzaqMSu29ysXQJYXw
✅ Preview: https://css-text-portrait-builder-git-fork-decantyme-dev-warengonzaga.vercel.app

[warengonzaga]

All good to me! I like what you did to export the builds by creating a post-build script. 😊
Meaning if you want to use parcel (zero-config) you still need to config it when you want to export a serverless version of your builds. 😅

The question, any instructions on how to export your builds? So I can add it to the official documentation. 🤔

[decanTyme]

All good to me! I like what you did to export the builds by creating a post-build script. 😊 Meaning if you want to use parcel (zero-config) you still need to config it when you want to export a serverless version of your builds. 😅

Thanks! 😊 and yeah I really couldn't find anything anywhere that allows Parcel to bundle it for non-production settings, which I guess is understandable since it primarily deals with live apps and is created with that in mind.

The question, any instructions on how to export your builds? So I can add it to the official documentation. 🤔

Oh right almost forgot about this, thanks again for reminding!

Docs:

Run yarn export:optimized to export and compress the build files. The resulting files do not need any servers to run (i.e. you can open it directly in a browser without using a dev server.) The compressed (zip) file will be saved inside dist/. To export without minification and other optimizations, run yarn export. For convenience, there is a yarn compress script that you can use if you do not want the postbuild script to run, which is used to prepare the files for running without a server.

Something like that I guess?

[warengonzaga]

Run yarn export:optimized to export and compress the build files. The resulting files do not need any servers to run (i.e. you can open it directly in a browser without using a dev server.) The compressed (zip) file will be saved inside dist/. To export without minification and other optimizations, run yarn export. For convenience, there is a yarn compress script that you can use if you do not want the postbuild script to run, which is used to prepare the files for running without a server.

That's it! We can improve it later... 😊 @decanTyme

[warengonzaga]

@decanTyme I'm happy to merge this now...