Skip to content

Copying assets from node module #3859

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
samherrmann opened this issue Jan 5, 2017 · 3 comments
Closed

Copying assets from node module #3859

samherrmann opened this issue Jan 5, 2017 · 3 comments

Comments

@samherrmann
Copy link

samherrmann commented Jan 5, 2017

Please provide us with the following information:

OS?

Windows 7

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:

...
"assets": [
    "assets",
    "favicon.ico",
    "../node_modules/cesium/Build/Cesium"
 ],
...

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.

@samherrmann samherrmann changed the title Copying assets from node module into assets folder Copying assets from node module Jan 5, 2017
@jsanchezgarcia
Copy link
Contributor

@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

@filipesilva
Copy link
Contributor

@jsanchezgarcia is right. #3555 is tracking the enhancement.

@angular-automatic-lock-bot
Copy link

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

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants