Create binary of spaCy with PyInstaller

I would like to create a binary of my python code, that contains spaCy.

# main.py

import spacy
import en_core_web_sm

def main() -> None:
    nlp = spacy.load("en_core_web_sm")
    # nlp = en_core_web_sm.load()
    doc = nlp("This is an example")
    print([(w.text, w.pos_) for w in doc])

if __name__ == "__main__":
    main()

Besides my code, I created two PyInstaller-hooks, as described here

To create the binary I use the following command pyinstaller main.py --additional-hooks-dir=..

On the execution of the binary I get the following error message:

Traceback (most recent call last):
  File "main.py", line 19, in <module>
    main()
  File "main.py", line 12, in main
    nlp = spacy.load("en_core_web_sm")
  File "spacy/__init__.py", line 47, in load
  File "spacy/util.py", line 329, in load_model
OSError: [E050] Can't find model 'en_core_web_sm'. It doesn't seem to be a Python package or a valid path to a data directory.

If I use nlp = en_core_web_sm.load() instead if nlp = spacy.load("en_core_web_sm") to load the spacy model, I get the following error:

Traceback (most recent call last):
  File "main.py", line 19, in <module>
    main()
  File "main.py", line 13, in main
    nlp = en_core_web_sm.load()
  File "en_core_web_sm/__init__.py", line 10, in load
  File "spacy/util.py", line 514, in load_model_from_init_py
  File "spacy/util.py", line 389, in load_model_from_path
  File "spacy/util.py", line 426, in load_model_from_config
  File "spacy/language.py", line 1662, in from_config
  File "spacy/language.py", line 768, in add_pipe
  File "spacy/language.py", line 659, in create_pipe
  File "thinc/config.py", line 722, in resolve
  File "thinc/config.py", line 771, in _make
  File "thinc/config.py", line 826, in _fill
  File "thinc/config.py", line 825, in _fill
  File "thinc/config.py", line 1016, in make_promise_schema
  File "spacy/util.py", line 137, in get
catalogue.RegistryError: [E893] Could not find function 'spacy.Tok2Vec.v1' in function registry 'architectures'. If you're using a custom function, make sure the code is available. If the function is provided by a third-party package, e.g. spacy-transformers, make sure the package is installed in your environment.