From c254b4ccec47b549deddc34c5b7f0ba090c543b6 Mon Sep 17 00:00:00 2001
From: valadaptive <valadaptive@protonmail.com>
Date: Mon, 24 Nov 2025 08:49:19 -0500
Subject: [PATCH 1/2] Add warning about using this for worker threads

---
 README.md | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index e6523ba..5cd6bdf 100644
--- a/README.md
+++ b/README.md
@@ -11,7 +11,7 @@ Serialize JavaScript to a _superset_ of JSON that includes regular expressions,
 
 The code in this package began its life as an internal module to [express-state][]. To expand its usefulness, it now lives as `serialize-javascript` — an independent package on npm.
 
-You're probably wondering: **What about `JSON.stringify()`!?** We've found that sometimes we need to serialize JavaScript **functions**, **regexps**, **dates**, **sets** or **maps**. A great example is a web app that uses client-side URL routing where the route definitions are regexps that need to be shared from the server to the client. But this module is also great for communicating between node processes.
+You're probably wondering: **What about `JSON.stringify()`!?** We've found that sometimes we need to serialize JavaScript **functions**, **regexps**, **dates**, **sets** or **maps**. A great example is a web app that uses client-side URL routing where the route definitions are regexps that need to be shared from the server to the client.
 
 The string returned from this package's single export function is literal JavaScript which can be saved to a `.js` file, or be embedded into an HTML document by making the content of a `<script>` element.
 
@@ -19,6 +19,13 @@ The string returned from this package's single export function is literal JavaSc
 
 Please note that serialization for ES6 Sets & Maps requires support for `Array.from` (not available in IE or Node < 0.12), or an `Array.from` polyfill.
 
+> [!WARNING]
+> It may be tempting to use this package as a way to pass arbitrary functions into [worker threads](https://nodejs.org/api/worker_threads.html), since you cannot pass them directly via `postMessage()`. However, passing functions between worker threads is not possible in the general case. This package lets you serialize *some* functions, but it has limitations.
+>
+> For instance, if a function references something from outside the function body, it will not run properly if serialized and deserialized. This could include [closed-over variables](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Closures) or imports from other packages. For a serialized function to run properly, it must be entirely self-contained.
+>
+> In general, it is not possible to send arbitrary JavaScript to a worker thread, and pretend it's running the same way it would run on the main thread. This package doesn't let you do that.
+
 ## Installation
 
 Install using npm:

From cb95ca8d9ee2cbd1f12136ab6cc7cd136c4f6ad7 Mon Sep 17 00:00:00 2001
From: valadaptive <valadaptive@protonmail.com>
Date: Wed, 26 Nov 2025 11:20:51 -0500
Subject: [PATCH 2/2] Referenceify links

---
 README.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 5cd6bdf..8d302e8 100644
--- a/README.md
+++ b/README.md
@@ -20,9 +20,9 @@ The string returned from this package's single export function is literal JavaSc
 Please note that serialization for ES6 Sets & Maps requires support for `Array.from` (not available in IE or Node < 0.12), or an `Array.from` polyfill.
 
 > [!WARNING]
-> It may be tempting to use this package as a way to pass arbitrary functions into [worker threads](https://nodejs.org/api/worker_threads.html), since you cannot pass them directly via `postMessage()`. However, passing functions between worker threads is not possible in the general case. This package lets you serialize *some* functions, but it has limitations.
+> It may be tempting to use this package as a way to pass arbitrary functions into [worker threads][], since you cannot pass them directly via `postMessage()`. However, passing functions between worker threads is not possible in the general case. This package lets you serialize *some* functions, but it has limitations.
 >
-> For instance, if a function references something from outside the function body, it will not run properly if serialized and deserialized. This could include [closed-over variables](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Closures) or imports from other packages. For a serialized function to run properly, it must be entirely self-contained.
+> For instance, if a function references something from outside the function body, it will not run properly if serialized and deserialized. This could include [closed-over variables][] or imports from other packages. For a serialized function to run properly, it must be entirely self-contained.
 >
 > In general, it is not possible to send arbitrary JavaScript to a worker thread, and pretend it's running the same way it would run on the main thread. This package doesn't let you do that.
 
@@ -148,3 +148,5 @@ See the [LICENSE file][LICENSE] for license text and copyright information.
 [express-state]: https://github.com/yahoo/express-state
 [JSON.stringify]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify
 [LICENSE]: https://github.com/yahoo/serialize-javascript/blob/main/LICENSE
+[worker threads]: https://nodejs.org/api/worker_threads.html
+[closed-over variables]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Closures
\ No newline at end of file