Publishing substrate-lib components as a separate npm package? about substrate-front-end-template

[jimmychu0807]

@shawntabrizi feedback copied here for reference

we should think about the long term maintainence required here. Does it make sense for a package like this to be included with the Polkadot-JS stuff? As in, rather than making another library which ultimately depends on Polkadot-JS, we include it with the Polkadot-JS ecosystem and have them maintain it in the future?

We really should evalute the value add here. The point of the Substrate UI is not necessarily to provide a set of libraries for the user, but just to show them how things can be done. The libraries at the end of the day are the Polkadot JS API stuff

I don't expect many people to actually build their final front end using the front-end template, rather it will be the first starting point for tutorials or for people to hack on, and a great way to reference how to do X.

[jimmychu0807]

thought: replace the result of substrate-ui-new with front-end-template?

[shawntabrizi]

thought: replace the result of substrate-ui-new with front-end-template?

@jimmychu0807 there is already a PR for this: https://github.com/paritytech/substrate-up/pull/39/files

Waiting for us to move to the new version of the docs to merge it as it will break a lot of our initial setup instructions