[Question] Sourcing components

[mauleb]

Description

I'm struggling to find documentation for the registry or any UI to browse components. Additionally a lot of the components under serverless-components seem to be outdated at this point.

I saw that there was a way to reference components on NPM or local but those might of been abandoned? If I want to create a custom component for my use case then I have to publish it publicly to your registry?

Beyond some very "basic" components such as website and aws-dynamodb i haven't had any luck with getting things working with the above in mind.

[eahefnawy]

Thanks for reaching out @mauleb ... we currently don't have a UI for the registry, we're working on it though. Right now we just have a static-ish page that lists all the available components in the Serverless Dashboard when you create an app. Soon, we should have a more dynamic UI though.

Regarding building components, here are the latest docs: https://github.com/serverless/components#building-components

Curious, what are your use case beyond the "basics"?

[mauleb]

@eahefnawy Thanks for the quick response.

Right now we just have a static-ish page that lists all the available components in the Serverless Dashboard when you create an app.

I don't see the components list on the dashboard at the moment. Whats the specific url? https://app.serverless.com/user/?

Regarding building components, here are the latest docs: https://github.com/serverless/components#building-components

I did see the documentation for building and publishing components, but I didn't see a way to either publish privately or reference a component that is defined locally.

Curious, what are your use case beyond the "basics"?

Well first of all, my needs are pretty basic in general. I quoted the word because the underlying mechanics of the website component are more complex and calling it basic felt a little hand wavy. Sure the components are basic from a consumer perspective which is the goal. The main problem is that some of the repos under serverless-components are outdated and can't be used directly. One use case in particular I was looking for was as websocket based api but those components are currently throwing errors. With that in mind, I was hoping to throw together a basic imitation and deploy it without publishing it but no luck so far.

[mauleb]

@eahefnawy Is there documentation for what steps are required to use private / local defined components?

[eahefnawy]

@mauleb we don't support private components atm. Also, all components run in the cloud, so you must publish to test. I suggest you run sls publish --dev to skip versioning for a faster feedback loop.

[mauleb]

@eahefnawy Is this no longer true?

[mwawrusch]

To add to that, there seem to be a lot of unhandled bugs, like this one: https://github.com/serverless-components/aws-lambda/issues/29 - which makes the whole project unusable, unless there is at least a workaround. I understand where you are heading with serverless components but you need to fix the existing components, remove (hide, archive, move to a different repo) the outdated ones, and hire a technical writer to rebuild some trust. And maybe add a zapier integration so that you don't have dangling issues that are months old in repos because you don't get notified.

Also, it would be really helpful to have some real-world sample project, and some integration that shows webpack/typescript as well. That's pretty standard in 2020...