webalys-hq / streamlinehq-npm

The deprecated Streamline NPM package, which will be deleted on 1st November 2022.
https://medium.com/streamline-icons/how-streamline-narrows-down-its-focus-eac6fdb5c6f2
24 stars 5 forks source link

Ability to set destination of images #3

Closed w0ofy closed 3 years ago

w0ofy commented 3 years ago

The ask

Would it be possible to configure a way to set the destination of the images directory.

The why

My team is building a (private, not open source) design system / component library and we want to include assets in the component library package, so consumer applications don't need to install streamline packages. It's not ideal to require consumer applications to configure streamline's npm registry -- this becomes particularly cumbersome in CI/CD workflows.

cbrwizard commented 3 years ago

Ok let me try to paraphrase what you're saying. You have a number of apps (AppA, AppB) which use a component Library. Some components in your Library use Streamline icons from this streamlinehq package. You want to install Library in AppA and AppB but you want to provide a configuration file streamlinehq.json only in Library itself, not in AppA or AppB, right?

If that's so, how do you think this should be solved? How would allowing to set destination of the images directory help?

cbrwizard commented 3 years ago

Today we announce that we're deprecating the Streamline NPM package. Instead, we’ll focus on the web app and Figma plugin, which are used by a noticeable share of our customers.

Please from now on instead of using our brittle package download the images directly from our website and insert them into your project as SVG files. Meanwhile, Streamline team is focused on ensuring that our web application provides the best user experience for developers' use cases. Please take 2 minutes to share feedback so that we can improve.

We'll keep this package with minimal life support until 1st November 2022, after which it's going to be deleted.

Please read the full story in this article.