You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 4, 2025. It is now read-only.
4. Create a production build using build-optimizer
ng build --prod --aot --build-optimizer
The log given by the failure
Uncaught TypeError: Cannot read property 'call' of undefined
Desired functionality
In the example above, it should display the quill-editor library when using the build-optimizer flag.
Mention any other details that might be useful
createTslibImport is being called in build-optimizer/src/transforms/import-tslib even if it doesn't pass the criteria set in testImportTslib (e.g. using webpack_require).
Adding a new check on line 41 (isHelperName(name) && testImportTslib(name)) fixes this issue. I'm not sure if that's the right solution as it seems to be just a helper function. Maybe create a new one that checks if it's using __webpack_require__?
The text was updated successfully, but these errors were encountered:
Bug Report or Feature Request (mark with an
x
)Area
Versions
build-optimizer: 0.0.41
Node: v9.4.0
OS: macOS High Sierra
Repro steps
1. Create a new angular-cli installation and install ngx-quill:
2. Import ngx-quill to src/app/app.module.ts
3. Add quill-editor to your component template:
4. Create a production build using build-optimizer
The log given by the failure
Uncaught TypeError: Cannot read property 'call' of undefined
Desired functionality
In the example above, it should display the
quill-editor
library when using thebuild-optimizer
flag.Mention any other details that might be useful
createTslibImport
is being called inbuild-optimizer/src/transforms/import-tslib
even if it doesn't pass the criteria set intestImportTslib
(e.g. using webpack_require).Adding a new check on line 41 (
isHelperName(name) && testImportTslib(name)
) fixes this issue. I'm not sure if that's the right solution as it seems to be just a helper function. Maybe create a new one that checks if it's using__webpack_require__
?The text was updated successfully, but these errors were encountered: