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
This issue follows the comment made in issue #2837. @filipesilva suggested to copy complex libraries, such as Cesium, into the assets folder. Building on that suggestion, I changed my angular-cli.json file to the following:
With this configuration, I expected to find a Cesium folder within the dist folder when runningng build. That is however not the case. No errors are encountered during the build, but the folder is not copied into dist. When I run tests by adding other folders within src to assets, then that works as expected.
The text was updated successfully, but these errors were encountered:
samherrmann
changed the title
Copying assets from node module into assets folder
Copying assets from node module
Jan 5, 2017
@samherrmann it seems that relative paths are not supported (see #2933). Looking at that issue and at #2837 (comment) it seems that the best way to deal with this is to to manually copy the needed assets into the assets folder
OS?
Versions.
angular-cli: 1.0.0-beta.24
node: 6.9.1
os: win32 x64
@angular/common: 2.4.1
@angular/compiler: 2.4.1
@angular/core: 2.4.1
@angular/forms: 2.4.1
@angular/http: 2.4.1
@angular/platform-browser: 2.4.1
@angular/platform-browser-dynamic: 2.4.1
@angular/router: 3.4.1
@angular/compiler-cli: 2.4.1
Repro steps.
This issue follows the comment made in issue #2837. @filipesilva suggested to copy complex libraries, such as Cesium, into the assets folder. Building on that suggestion, I changed my
angular-cli.json
file to the following:With this configuration, I expected to find a Cesium folder within the
dist
folder when runningng build
. That is however not the case. No errors are encountered during the build, but the folder is not copied intodist
. When I run tests by adding other folders withinsrc
toassets
, then that works as expected.The text was updated successfully, but these errors were encountered: