Satis Reviews

Parcel Reviews

Satis mentions (5)

• Need help with Installing Enlightn Pro

  Note: Satis is a local repo repository — the pro code is likely not on github. They set up their own system to handle these repositories outside of github/packagist. Source: over 1 year ago

• Private Packagist - has anyone used and can tell me if it might fit in my scenario?

  If you want/need to self-host this internally, you can look at satis to create and self-host a repository. Since you need to add the packages manually, your security team can vet the code before adding it. There is a post on gitconnected on how to set this up: https://levelup.gitconnected.com/how-to-host-your-own-private-packagist-for-free-or-extremely-cheap-faf44eca3647. Source: almost 2 years ago

• Need a secured way to be able to use Composer

  We have a private Satis instance. Our ITSec team reviews all packages before we add them to Satis. Packagist.com is available for us but the CI-CD servers can reach only the private Satis. Source: almost 2 years ago

• My own CMS/Tool - what is the best way to go about the usage in different projects?

  My team and I use Satis to accomplish that. It's hosted on our servers and we can easily release new versions. Dependabot can even upgrade the dependencies if new ones are detected. Source: almost 2 years ago

• Do you use a private composer registry ? (Why / Why Not)

  Composer supports multiple types of custom respositories, so you can host your own repository (with something like Satis), pay for a packagist.com private repository or even use a VCS repository to fetch packages directly from your private GIT repos. Source: over 2 years ago

Parcel mentions (103)

• Create a typescript package with Parcel

  Parcel is a fast and zero-configuration web application bundler designed to simplify the build process for modern web projects. It's not limited to web applications, and it can be used to build packages targeting the browser or Node.js. - Source: dev.to / about 1 month ago

• How and why do we bundle zx?

  At first we wanted to just get rid of all the helper utilities. Keep only the kernel, but this would mean a loss of backward compatibility. We needed some efficient code processing instead with recomposition and tree-shaking. We needed a bundler. But which one? Our testing approach relies on targets, not sources. We rebuilt the project frequently, speed was critical requirement. In essence, we chose a solution... - Source: dev.to / about 2 months ago

• DEMO - Voice to PDF - Complete PDF documents with voice commands using the Claude 3 Opus API

  It runs using Parcel, very simple and easy to setup. The app has 3 files:. - Source: dev.to / about 2 months ago

• React Server Components Example with Next.js

  In the Changelog Podcast episode referenced above, Dan Abramov alluded to Parcel working on RSC support as well. I couldn’t find much to back up that claim aside from a GitHub issue discussing directives and a social media post by Devon Govett (creator of Parcel), so I can’t say for sure if Parcel is currently a viable option for developing with RSCs. - Source: dev.to / 2 months ago

• Build a Vite 5 backend integration with Flask

  Once you build a simple Vite backend integration, try not to complicate Vite's configuration unless you absolutely must. Vite has become one of the most popular bundlers in the frontend space, but it wasn't the first and it certainly won't be the last. In my 7 years of building for the web, I've used Grunt, Gulp, Webpack, esbuild, and Parcel. Snowpack and Rome came-and-went before I ever had a chance to try them.... - Source: dev.to / 4 months ago