-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Localhost set up Polymer 1.0 #4869
Comments
What kind of project do you have? See docs for element project and application project. You'll need to use other project templates for 1.x though, see this issue. /cc @arthurevans |
I would like to set up an elements project I believe. I need to use polymer 1.0 The polymer programming I have done so far has been using HTML files and importing bower components at the start of each document then calling an instance of that component. |
Probably port 8080 is already in use, so polymer serve is using 8081. |
Returns "not found" |
update: If I navigate to |
Looks like port 8081 since you're having errors |
That produces the right page. Looks like Polymer serve is working now thank you all! Can I set something up that will work in a similar way? Thanks again |
If I get it right, you can follow the same structure, in components folder, to build your own component. Then you can publish or wrap it for your own use. |
It sounds like you got the help you were looking for so I'm going to close this issue. |
I am trying to set up polymer 1.0 on my Apple Mac.
I have been able to install Git, Node JS, Atom and Bower fine but I am not getting anything on any local host.
I have followed instructions on Polymer Project website but when running the polymer serve command in terminal in project directory I get nothing at localhost:8080/components/icon-toggle/demo/
I have attached the response I get from the polymer serve command in terminal. I have also tried to navigate to the link shown in the image but get a page not found error.
Quite new to this so any help is largely appreciated.
The text was updated successfully, but these errors were encountered: