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

Use npm instead of tarball for the geostyler-css-parser #5765

Closed
1 task done
allyoucanmap opened this issue Aug 11, 2020 · 2 comments
Closed
1 task done

Use npm instead of tarball for the geostyler-css-parser #5765

allyoucanmap opened this issue Aug 11, 2020 · 2 comments

Comments

@allyoucanmap
Copy link
Contributor

Description

We are installing the geostyler-css-parser via tarball but we should use npm instead. Check if the pending PR has been merged at the time this issue is in progess. If it's not merged we should move the branch used by tarball under the geosolutions-it repository and create a new package @geosolutions/geostyler-geocss-parser and replace the import where needed.

"geostyler-geocss-parser": "https://github.com/allyoucanmap/geostyler-geocss-parser/tarball/build",

What kind of improvement you want to add? (check one with "x", remove the others)

  • Other... Please describe: Library dependency

Other useful information

@allyoucanmap
Copy link
Contributor Author

We should also take into account following related libraries and evaluate if the fork is needed:

  • geostyler-style
  • geostyler-sld-parser
  • geostyler-openlayers-parser
  • flat-geo-css

@allyoucanmap
Copy link
Contributor Author

see also this #6933 (comment)

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