# Seeing encrypted:ciphertext only?

[← Back to Next.js](https://dotenvx.com/docs/nextjs.md#ship)

Next.js may still be using the original @next/env package, even after adding the override. Check which package is installed:

**npm**

```console
$ npm ls @next/env
```

**pnpm**

```console
$ pnpm why @next/env
```

The output should show @next/env as an alias of @dotenvx/next-env. An original Next.js version followed by “overridden” does not mean the replacement was installed.

If the original package is still installed, stop the dev server with Ctrl+C. From your project directory, rebuild the dependency installation:

**npm**

```console
$ rm -rf node_modules package-lock.json
$ npm install
$ npm ls @next/env
```

**pnpm**

```console
$ rm -rf node_modules pnpm-lock.yaml
$ pnpm install
$ pnpm why @next/env
```

Confirm the alias now points to @dotenvx/next-env, then restart:

**npm**

```console
$ npm run dev
```

**pnpm**

```console
$ pnpm dev
```

Refresh [/api/hello](http://localhost:3000/api/hello). Review the regenerated lockfile before committing, since reinstalling can update dependency versions.