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

Publish to npm #148

Closed
bartvde opened this issue Jun 26, 2017 · 6 comments
Closed

Publish to npm #148

bartvde opened this issue Jun 26, 2017 · 6 comments

Comments

@bartvde
Copy link

bartvde commented Jun 26, 2017

As initially discussed here: #145 (comment)

this ticket describes my use case for wanting to publish maputnik to npm.

So in my React-Redux based project I plan to integrate the LayerEditor component of Maputnik to facilitate symbology editing without having to write it from scratch. I can use a git connection string for now, but better would be to have actual releases get pushed to npmjs as well

@orangemug
Copy link
Collaborator

So in my React-Redux based project I plan to integrate the LayerEditor component of Maputnik

@bartvde it would be great to get details of this if you are able to share. I've been meaning to raise a ticket for a while to ask everybody where all our (mainly @lukasmartinelli) hard work is getting put to good use.

@bartvde
Copy link
Author

bartvde commented Jun 26, 2017

sure, it is still work in progress (prototype stages), but once we have it hammered out we will definitely share it

@bartvde
Copy link
Author

bartvde commented Jun 26, 2017

We have an SDK (https://github.com/boundlessgeo/sdk) which we are porting over to use redux (it was still flux based) and want to use maputnik style editing components later on, my small prototype is here: https://github.com/bartvde/layerstore-test

@orangemug
Copy link
Collaborator

Maybe we should add a 'used by these people' section to our readme / new website.

Thoughts @lukasmartinelli ?

@orangemug
Copy link
Collaborator

Ok anyway back to npm publishing. We should definitely do this. I'll look to automate it via travis so tagged commits get auto published to npm, I think I've done this before... I'll have to dig through some old code and take a look. I think I'll need @lukasmartinelli to configure the private keys on travis also.

I'll have a look and report back.

@orangemug
Copy link
Collaborator

From #164 (comment)

we have actually taken a different approach since and are not using maputnik anymore

Closing the issue for now if anyone needs this, please shout and we'll reopen.

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

No branches or pull requests

2 participants