Weaver folder causes ilpostprocessorrunner when Mirror is used in a local package

[Zibelas]

Describe the bug Using Mirror in a local package that gets imported into another project is throwing a lot of ilpostprocessorrunner error.

[IMPORTANT] How can we reproduce the issue, step by step: -> Created a new project. -> Imported Mirror 65.0.0 (as well 66.0.8 to test) -> Created a package.json and .asmdef file. -> This causes no problems at all, compiles fine and Mirror can be used without problem. -> Created a second project, went to package manager and went to "Add package from disk", installing the the previous created package. -> A lot of errors as seen in the screenshot are thrown right away when the package gets imported

The problem seems to come from the Weaver folder, if I remove that one, the import does not fail and all scripts compile.

Expected behavior Able to create a personal helper package for reusing selfwritten templates that use Mirror.

Desktop (please complete the following information):

• OS: Windows 10
• Build target: already on import of package/ Android
• Unity version: 2021.1.15f
• Mirror branch: 65.0.0

[MrGadget1024]

Couple things:

1. Restarting Unity after importing Mirror is always required, per the ReadMe.
2. Why not just right-click the Mirror folder and select Export Package to create a UnityPackage that you can import into any project just by dragging it into the project pane or from the import menu.

[Zibelas]

1. The restart issue is not fixing it, it will fail at the exact same point.
2. Because I want my helper project not to be imported as an asset but under packages. This was working at one point but I'm not sure which version of Mirror broke it.

[MrGadget1024]

Is this still an issue with latest from asset store?

[MrGadget1024]

Closing for no response. We may at some point generate a Unity package manager package, but not soon.