-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
Document npm package support #243
Comments
@notramo can you help me understand the desired workflow? Since Plenti generates the project scaffolding itself, I assume you'd want to install it as a global dependency and not a project dependency. So would NPM just be a means of downloading the binary onto your computer? If that makes folks life easier, we could probably add npm support using goreleaser. Does NPM have OS awareness and a way of downloading / executing the appropriate binary? Some of the confusion may be Plenti's market positioning. The goal is to be more similar to Hugo than Gatsby. Ultimately I want to empower developers with base HTML/CSS/JS knowledge to build full fledged sites that can be edited by nontechnical users without having to wrestle with higher level concepts like auth, databases, server management, and complicated toolchains. Out of the box we have NPM scaffolding for Svelte and our router (Navaid), but I ultimately want to remove that. Ideally if you want to extend your system with NPM, you should be able to do that, but you should manage those tools outside of Plenti's build. That way if you want to bundle, transpile, etc, we'll get out of your way more and let you use whatever tools you want. I know that's a bit different than original discussion of downloading Plenti via NPM, but thought it might be useful to understand why we haven't fully embraced interoperability with the JS ecosystem. Here's a reference to a previous discussion about NPM support: #135 |
This question originally is not about downloading Plenti via NPM, but using NPM packages in Plenti projects. I was reading something about not supporting modules, because Plenti uses raw V8 without module support. But in other comments it mentioned that some kind of support is present for ES modules. Unfortunately, it's hard to find out without reading all the issues and PR discussions, and following the development closely. You can't expect every new Plenti user to do it. Maybe it's easier to give answer to exact questions, so I collected some of them:
|
Ah sorry I misunderstood the question. Here are some details:
|
There are several issues (both open and closed) in this repo, regarding npm package support.
What is the progress? Is it usable currently?
Please document it somewhere.
The text was updated successfully, but these errors were encountered: