Module '"@pnp/sp"' has no exported member 'sp'. not resolved in visual studio code

 The error message "Module '@pnp/sp' has no exported member 'sp'" typically occurs when there is a problem with your PnPjs import or if you're using an outdated version of PnPjs. To resolve this issue, follow these steps:

1. **Update PnPjs**:

   Ensure you are using an up-to-date version of PnPjs. Outdated versions might not have the 'sp' export. You can update PnPjs by running the following command in your project's root directory:

   ```bash

   npm install @pnp/sp

   ```

2. **Import the Correct PnPjs Modules**:

   PnPjs uses a modular structure where different parts of SharePoint functionality are organized into separate modules. Make sure you are importing the correct modules for your needs. For example, if you want to access the 'sp' object, you can import it as follows:

   ```javascript

   import { sp } from "@pnp/sp";

   ```

   Additionally, make sure you import any other modules you need for your specific use case. For example:

   ```javascript

   import "@pnp/sp/webs";

   import "@pnp/sp/lists";

   ```

3. **Check Your TypeScript Configuration**:

   Ensure that your TypeScript configuration (typically `tsconfig.json`) is set up correctly. The `@types/pnp` package should be automatically installed when you install `@pnp/sp`. If not, you can install it manually:

   ```bash

   npm install --save-dev @types/pnp

   ```

4. **Restart Visual Studio Code**:

   Sometimes, Visual Studio Code may not recognize the changes immediately. Restarting VS Code can help it pick up the latest changes and correctly identify the imported modules.

5. **Verify Package Versions**:

   Check your `package.json` file to make sure there are no version conflicts or duplicate packages that might be causing issues.

6. **IntelliSense and Caching**:

   Visual Studio Code sometimes has IntelliSense and caching issues. You can try to clear the editor's IntelliSense cache and restart VS Code.

7. **Rebuild Your Project**:

   After making the necessary changes, rebuild your project by running:

   ```bash

   gulp bundle --ship

   gulp package-solution --ship

   ```

   This ensures that any TypeScript changes are properly compiled and bundled.

After following these steps, you should be able to resolve the error related to the 'sp' export from '@pnp/sp'. If the issue persists, double-check your code for any syntax errors or typos in your import statements and code structure.