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

1.x projects not showing up in polymer init #2485

Open
arthurevans opened this issue Jun 19, 2017 · 24 comments
Open

1.x projects not showing up in polymer init #2485

arthurevans opened this issue Jun 19, 2017 · 24 comments

Comments

@arthurevans
Copy link

As the subject line says, latest version of the CLI appears to be missing 1.x projects:

$ polymer --version
1.2.0
$ polymer init
? Which starter template would you like to use? (Use arrow keys)
❯ polymer-2-element - A simple Polymer 2.0 element template 
  polymer-2-application - A simple Polymer 2.0 application 
  polymer-2-starter-kit - A Polymer 2.x starter application template, with navigation and "PRPL patt
ern" loading 
  shop - The "Shop" Progressive Web App demo 
@justinfagnani
Copy link
Contributor

This was done on purpose in CLI 1.2

@davidmaxwaterman
Copy link

Is there any way to get them back again? If not, then it's not a huge deal - I just often use that to see how it should be (eg I long ago removed my service worker code since I was forced to use http, but have recently been moved to https [yay!], so wanted to put it all back again). I always have my own git history...

@justinfagnani
Copy link
Contributor

I think we should make either a flag or a separate install of 1.x templates.

@elarb
Copy link

elarb commented Jun 19, 2017

Related PR: #782

@stramel
Copy link
Contributor

stramel commented Jun 19, 2017

@justinfagnani Maybe make them generators that can be installed like the custom build?

@justinfagnani
Copy link
Contributor

@stramel exactly. That's what I mean by a separate install

@abdonrd
Copy link
Contributor

abdonrd commented Jun 19, 2017

+1 to separate install!

@justinfagnani justinfagnani self-assigned this Jun 20, 2017
@stramel
Copy link
Contributor

stramel commented Jun 21, 2017

Needed this for work so I went ahead and created a separate generator for it. https://github.com/Hackception/generator-polymer-init-polymer-1-element

@justinfagnani
Copy link
Contributor

@stramel I just started that yesterday. If you don't mind could you hold off so we can publish to npm?

@stramel
Copy link
Contributor

stramel commented Jun 21, 2017

@justinfagnani Okay, if you need help let me know! I will just npm i -g . for now. I unpublished, the name is available.

@sebastianroming
Copy link

I use CLI 1.1.0 but don't get the Polymer 1 proposals. Yesterday it worked fine, I haven't updated anything.

@milesje
Copy link

milesje commented Jul 27, 2017

@justinfagnani @stramel any chance of the generator getting published to NPM?

@stramel
Copy link
Contributor

stramel commented Jul 27, 2017

@milesje I have one you can use but @justinfagnani wanted to publish under the same name so I left it open for him you can clone and then run npm i -g . from within that directory. Then run polymer init.

https://github.com/Hackception/generator-polymer-init-polymer-1-element

@z2oh
Copy link

z2oh commented Aug 15, 2017

@stramel Any chance you have one for the application template as well?

Can we get these templates on npm any time soon? I've seen others clambering for an easier solution to this problem on the Polymer Slack and elsewhere.

@stramel
Copy link
Contributor

stramel commented Aug 15, 2017

@z2oh I do not have it but I could probably get one out there within the week...

@davidmaxwaterman
Copy link

davidmaxwaterman commented Sep 27, 2017

This has come up for me again...any news on one published in npm? I don't see it and it's been a while since....June?
[edit] Ah, I'm after the application template....any news on that @stramel ?

@davidmaxwaterman
Copy link

Trying to follow @stramel 's instructions, I get an error regarding ansi-escapes....looks like one needs to run an 'npm install' in the directory itself before the global one. Perhaps it's obvious, but...

@davidmaxwaterman
Copy link

davidmaxwaterman commented Sep 27, 2017

It occurs to me that it would very nice if the polymer 1 options were kept/restored. I can imagine that they were removed because polymer engineers thought 'polymer starter kit' is only for people starting new projects, and they wanted people to start new projects with polymer 2. Unfortunately, that isn't the only reason people use PSK. My suggestion would be to keep the options as part of polymer-cli but don't show them in the list of options, meaning that the user has to know about it, and specifically request it in order to get it.
WDYT?

@stramel
Copy link
Contributor

stramel commented Sep 27, 2017

Dang guys I feel bad I never got that application template posted. I will try to get to it today!

UPDATE: I got the repo built out. Let me know if you have any issues with it.
https://github.com/Hackception/generator-polymer-init-polymer-1-application

@arthurevans
Copy link
Author

Ping @justinfagnani

@justinfagnani
Copy link
Contributor

@stramel thanks for posting that. We'd be will to pull that repo into the Polymer org

@tony19
Copy link
Contributor

tony19 commented Oct 7, 2017

In the meantime, installing those 1.x templates is possible with:

npm i -g \
 github:Hackception/generator-polymer-init-polymer-1-element \
 github:Hackception/generator-polymer-init-polymer-1-application
npm i -g justinfagnani/generator-polymer-init-polymer-1-element \
         justinfagnani/generator-polymer-init-polymer-1-application

@stramel
Copy link
Contributor

stramel commented Oct 7, 2017

Ahh my bad guys I attempted to do it from my phone then forgot to circle back to it.

@tony19 I had to move these to my personal account in order to transfer them to @justinfagnani since I don't have access to create repositories in the Polymer org 😢

I have sent the transfer request to @justinfagnani. Should hopefully be transferred by sometime next week!

@stale
Copy link

stale bot commented Mar 3, 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 3, 2020
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