# PackageCompiler app with proprietary modules, non "registered"

**URL:** https://discourse.julialang.org/t/packagecompiler-app-with-proprietary-modules-non-registered/77285
**Category:** General Usage
**Tags:** module, package-compiler, dependencies
**Created:** [March 2, 2022, 9:44am UTC](https://discourse.julialang.org/t/packagecompiler-app-with-proprietary-modules-non-registered/77285 "2022-03-02T09:44:03Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![xor0110](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/xor0110/32/7926_2.png) [@xor0110](https://discourse.julialang.org/u/xor0110)
#### Post date: [March 2, 2022, 9:44am UTC](https://discourse.julialang.org/t/packagecompiler-app-with-proprietary-modules-non-registered/77285/1 "2022-03-02T09:44:03Z")

</div>

I’m trying to use PackageCompiler with a microservice based on HTTP.jl. My project also depends on proprietary modules that are not FOSS projects in GitHub. Everything works fine if I run the code. `PackageCompiler.create_app`, though, fails complaining that dependencies should be “registered”. How do I get around this?