Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add tip to wrap .js files in a NPM package to avoid needing externs #95

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add tip to wrap .js files in a NPM package to avoid needing externs #95

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/release.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -174,6 +174,8 @@ global:SomeGlobalVariable

In this example the compiler will stop renaming `something.foo()`, `something.bar()`.

TIP: If you'd need to create a long `externs/<your-build>.txt` (maybe a library is generating `.js` files), you have the option to wrap your `.js` files in an NPM package by placing them in `packages/<your-package>`, running `npm init -y` and adding the build config `:js-options {:js-package-dirs ["node_modules" "packages"]}`. Doing so, your `.js` files will be treated like any other NPM package, so no externs required.

== Build Report [[build-report]]

`shadow-cljs` can generate a detailed report for your `release` builds which includes a detailed breakdown of the included sources and how much they each contributed to the overall size.
Expand Down