Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Any plans to publish to `@carbon/icon-build-helpers` to npm?

See original GitHub issue

What package(s) are you using?

carbon-components
carbon-components-react

Summary

In the README of the carbon/packages/icon-build-helpers repo, it states that it is a private module. Would you consider publishing the module to npm so that it can be consumed externally?

Relevant information

Issue Analytics

State:
Created 4 years ago
Comments:8 (4 by maintainers)

Top GitHub Comments

1reaction

joshblackcommented, Mar 4, 2020

Ah got it, so the hope is to use the vanilla builder from that package to get the build-info.json that is needed?

0reactions

metonymcommented, Mar 4, 2020

That would be great.

Exposing build-info.json in @carbon/icons would definitely solve the problem, without having to publish the internal icon-build-helpers!

Top Results From Across the Web

Creating and publishing scoped public packages - npm Docs

To share your code publicly in a user or organization namespace, you can publish public user-scoped or organization-scoped packages to the npm registry....

npm-publish - npm Docs

Description. Publishes a package to the registry so that it can be installed by name. By default npm will publish to the public...

package.json - npm Docs

Description. This document is all you need to know about what's required in your package. · name. If you plan to publish your...

Privacy Questions and Answers | npm Docs

When you publish a package to an Enterprise registry that npm hosts, or as a private package, npm makes all of that data...

surge - npm

Publish web apps to a CDN with a single command and no setup required. ... tear down a published project surge plan set...