How to use primeng as an external dependency

Type of Issue

Problem exporting other components of primeng

• [ X] Bug Report
• Feature Request

Description

I’ve been trying to creante a package with the packager. My app uses primeng but it says that the components of the library are not exported. The problem is with rollup:

‘InputSwitchModule’ is not exported by node_modules\primeng\primeng.js Error: ‘InputSwitchModule’ is not exported by node_modules\primeng\primeng.js at error (C:\Users\Hely\WebstormProjects\SysmarComponents\node_modules\rollup\dist\rollup.js:185:14) at Module.error (C:\Users\Hely\WebstormProjects\SysmarComponents\node_modules\rollup\dist\rollup.js:8390:3) at Module.trace (C:\Users\Hely\WebstormProjects\SysmarComponents\node_modules\rollup\dist\rollup.js:8487:10) at ModuleScope.findVariable (C:\Users\Hely\WebstormProjects\SysmarComponents\node_modules\rollup\dist\rollup.js:8093:22) at Node.bind (C:\Users\Hely\WebstormProjects\SysmarComponents\node_modules\rollup\dist\rollup.js:6996:31) at eachChild.child (C:\Users\Hely\WebstormProjects\SysmarComponents\node_modules\rollup\dist\rollup.js:5819:34) at value.forEach.child (C:\Users\Hely\WebstormProjects\SysmarComponents\node_modules\rollup\dist\rollup.js:5845:38) at Array.forEach (native) at keys.forEach.key (C:\Users\Hely\WebstormProjects\SysmarComponents\node_modules\rollup\dist\rollup.js:5845:11) at Array.forEach (native)

please describe the error that you encountered

How To Reproduce

Just use any component of primeng and then try to run ‘npm packager’

Expected Behaviour

Every package exported or at least a file where you can add the exported files

Version Information

ng-packagr: v1.2.0
node: v8.2.1
@angular: v4.4.4node
rxjs: 5.4.3
zone.js: 0.8.18
primeng: 2.0.6

[DavidParks8]

You should be able to build with primeng by utilizing the following addition to your ng-package config:

  {
    "lib": {
      "externals": {
        "primeng/primeng": "primeng"
      }
    }
  }

[github-actions[bot]]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

_{This action has been performed automatically by a bot.}