diff --git a/.gitignore b/.gitignore
index ab08da46..2e5747df 100644
--- a/.gitignore
+++ b/.gitignore
@@ -259,5 +259,5 @@ lerna-debug*
 
 samconfig.toml
 packaged.yaml
-.tgz
+*.tgz
 *.tar.gz
diff --git a/.npmignore b/.npmignore
new file mode 100644
index 00000000..55a725ff
--- /dev/null
+++ b/.npmignore
@@ -0,0 +1,13 @@
+*.ipynb
+*-test-project/
+*-test-project-*/
+.tap/
+cdk.out/
+docs/
+*.ts
+tests/
+coverage/
+.cache/
+.idea/
+.github/
+*.tgz
\ No newline at end of file
diff --git a/RELEASING.md b/RELEASING.md
index 50e5532f..f0ce6651 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -4,4 +4,4 @@ In order to release a new version of the project:
 
 1. Update the package version with `npm version <version>` to apply that version across all sub packages. If the Major version has changed, the Macro name will be automatically updated by [the sync-macro-version script](scripts/sync-macro-version.cjs)
 2. Push these changes (`git push --tags`)
-3. Draft a new release in GitHub (the CI will do the publish to npm) with the same name as the version tag. If you select "pre-release", this will be published in NPM as a `next` label so it will only be installed by users who explictly request the `@next` version.
+3. Draft a new release in GitHub (the CI will do the publish to npm) with the same name as the version tag. If you select "pre-release", this will be published in NPM as a `next` label so it will only be installed by users who explicitly request the `@next` version.