# FakerPress & Acorn 3

**URL:** https://discourse.roots.io/t/fakerpress-acorn-3/24866
**Category:** acorn
**Tags:** sage10
**Created:** 2023-02-27T13:48:07Z
**Posts:** 6

## Post 1 by @Twansparant — 2023-02-27T13:48:07Z

Hi there,

When developing a new site locally, I use [FakerPress](https://wordpress.org/plugins/fakerpress/) a lot to generate dummy content to test long post titles, content, pagination etc.

This used to work fine when installing & activating with composer, but since I updated to Acorn 3, I’m getting this error when activating the plugin:

```
Skipping provider [Carbon\Laravel\ServiceProvider] because it requires a dependency that cannot be found.
```

[Here’s my full error stack](https://flareapp.io/share/oPRgZqk7#F17).  
I can see the plugin uses **Carbon** , but I don’t really understand the root of this problem… What does Acorn have to do with this? Plugins should work as standalone applications right?

Is there a way to fix this error?

---

## Post 2 by @talss89 — 2023-02-27T15:40:27Z

Hi @Twansparant,

If everything is working as expected, I think you can safely ignore this.

[Acorn iterates over Laravel `ServiceProvider`s and attempts to load them](https://flareapp.io/share/oPRgZqk7#F15). A Laravel `ServiceProvider` is [bundled as part of `nesbot/carbon`](https://github.com/briannesbitt/Carbon/blob/1aec3f8d66ea86c3c9bb4ed0f6b31b156cfc1288/src/Carbon/Laravel/ServiceProvider.php).

I believe this error is thrown simply because Acorn is being smart about trying to boot the Carbon ServiceProvider, but associated dependencies aren’t installed.

You should be able to selectively disable auto-discovery of of a service provider by adding something like this to your `composer.json`:

```
"extra": {
    "laravel": {
        "dont-discover": [
            "nesbot/carbon"
        ]
    }
},
```

That’s all untested, but hopefully points in the right direction!

---

## Post 3 by @Twansparant — 2023-02-27T18:18:39Z

> [@talss89](#):
>
> If everything is working as expected, I think you can safely ignore this.

Hi @talss89, thanks for your reply!  
That’s just the thing, the whole backend is not working anymore when I activate the plugin. I only get the error screen on each admin page.

I tried what you suggested by editing my composer file but that did not fix it unfortunately…

Any other thoughts?  
Thanks!

---

## Post 4 by @Twansparant — 2023-02-28T13:34:03Z

Somehow I made it work by running:

```
wp @development acorn package:discover
```

Activating the plugin doesn’t throw an error now! :tada:

---

## Post 5 by @talss89 — 2023-03-01T12:10:41Z

Brilliant, thanks for sharing - that’s useful to know!

Did you retain the `extra.laravel` props in `composer.json`? Or were you able to remove that?

---

## Post 6 by @Twansparant — 2023-05-30T10:19:47Z

Sorry for my late reply, I was able to remove the `extra.laravel` props yes, running `wp @development acorn package:discover` was enough!