Skip to content
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

Allow customizing bower component directory #895

Closed
rictic opened this issue Dec 6, 2017 · 4 comments
Closed

Allow customizing bower component directory #895

rictic opened this issue Dec 6, 2017 · 4 comments

Comments

@rictic
Copy link
Contributor

rictic commented Dec 6, 2017

From @aaronanderson on April 29, 2017 17:22

In my project I have edited the .bowerrc file to set the bower directory to assets rather than bower_components. When I open up my Polymer 2.0 components in Atom all of my imports have Linter errors due to the insertion of a reference to a non-existent bower_components directory.

Example Import in file /home/dev/git/my-app/src/main/webapp/ui/my-app.html:

Example Linter error:
Error polymer-ide Unable to load import: ENOENT: no such file or directory, open '/home/dev/git/my-app/src/main/webapp/ui/bower_components/assets/polymer/polymer-element.html'

This directory does not exist but /home/dev/git/my-app/src/main/webapp/assets/polymer/polymer-element.html does and the app works fine with polymer serve.

I am using Atom 1.16.0 and polymer-ide version 0.3.0.

Copied from original issue: Polymer/atom-plugin#58

@rictic rictic changed the title Import errors when the Bower components directory changed from bower_components Allow customizing bower component directory Dec 6, 2017
@tedium-bot
Copy link
Collaborator

Issue migrated to polymer/tools#491

@aomarks aomarks transferred this issue from Polymer/polymer-editor-service Jan 3, 2019
@aomarks
Copy link
Member

aomarks commented Jan 3, 2019

Re-opening because this original issue is now transferred and canonical again.

@aomarks aomarks reopened this Jan 3, 2019
@stale
Copy link

stale bot commented Mar 4, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Mar 4, 2020
@stale
Copy link

stale bot commented Apr 29, 2022

This issue has been automatically closed after being marked stale. If you're still facing this problem with the above solution, please comment and we'll reopen!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants