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

Add flag to change which folder is the "base" for -o, input or output #1646

Closed
dfreedm opened this issue Feb 20, 2014 · 8 comments
Closed

Add flag to change which folder is the "base" for -o, input or output #1646

dfreedm opened this issue Feb 20, 2014 · 8 comments
Assignees

Comments

@dfreedm
Copy link
Member

dfreedm commented Feb 20, 2014

Default will be "input", add -r or --rel-to-output

@simshanith
Copy link

Would this allow me to use absolute URLs to imports? E.g. '/path/to/local/import' could be resolved from any other local path using this option?

@dfreedm
Copy link
Member Author

dfreedm commented Feb 27, 2014

That sounds like you want a different option that sets the server root. This issue was for allowing the creation of a build that can be copied into multiple folders and keep the same path information.

@simshanith
Copy link

Thanks for clarifying. Is there an open issue for the server root option feature? I noticed by default they are excluded with the /^\// pattern. Major blocker for ease of use in my opinion.

@dfreedm
Copy link
Member Author

dfreedm commented Feb 27, 2014

Not yet it doesn't, but that sounds like a reasonable thing to add. I'll open another issue to track that.

@constantx
Copy link

👍

@dfreedm dfreedm self-assigned this Aug 7, 2014
@kincaidoneil
Copy link

👍

What's the status of this...? I'd certainly find it very useful!

@pflannery
Copy link

👍 I need the base path to be based on my output path

if I have vulcanize -o dist/index.html app/index.html I end up with paths beginning with ../app or if I use --abspath . I end up with paths beginning with /, neither of these are desirable for my situation...

@dfreedm
Copy link
Member Author

dfreedm commented May 22, 2015

This bug is no longer relevant. As of 1.0, vulcanize allows for custom file loaders and returns text instead of writing files.

@dfreedm dfreedm closed this as completed May 22, 2015
@aomarks aomarks transferred this issue from Polymer/polymer-bundler Jan 3, 2019
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

6 participants