more

Author: msonnb

docs/platforms/javascript/guides/aws-lambda/install/npm.mdx

@@ -104,7 +104,9 @@ To set environment variables, navigate to your Lambda function, select **Configu
 
 ![](./img/env_vars.png)
 
-**For ESM functions only:** You'll also need to manually wrap your handler as shown below:
+<Alert level="info" title="For ESM Lambda Functions">
+
+You'll also need to manually wrap your handler as shown below:
 
 ```javascript {tabTitle:ESM} {filename:index.mjs}{1,3}
 import * as Sentry from "@sentry/aws-serverless";
@@ -114,13 +116,15 @@ export const handler = Sentry.wrapHandler(async (event, context) => {
 });
 ```
 
+</Alert>
+
 That's it - make sure to re-deploy your function and you're all set!
 
 ### Option B: Manual Setup
 
 To further customize the SDK setup, you can also manually initialize the SDK in your lambda function. The benefit of this installation method is that you can fully customize your Sentry SDK setup in a `Sentry.init` call.
 
-#### For CommonJS Functions
+#### For CommonJS Lambda Functions
 
 You can initialize the SDK directly in your main handler file:
 
@@ -155,14 +159,16 @@ Sentry.init({
   // ___PRODUCT_OPTION_END___ profiling
 });
 
+// Your package imports
+
 exports.handler = Sentry.wrapHandler(async (event, context) => {
   // Your handler code
 });
 ```
 
-It's important to add both, the `Sentry.init` call outside the handler function and the `Sentry.wrapHandler` wrapper around your function to automatically catch errors and performance data.
+It's important to add both, the `Sentry.init` call outside the handler function and the `Sentry.wrapHandler` wrapper around your function to automatically catch errors and performance data. Make sure that the `Sentry.init` call and the import statement are at the very top of your file before any other imports.
 
-#### For ESM Functions
+#### For ESM Lambda Functions
 
 First, wrap your handler: