ultimate-saas-ts VS cross-env

Stripe. I open-sourced my stack for building a SAAS project: https://github.com/gmpetrov/ultimate-saas-ts

It took 2-3month to build the project. But I leverage lots of parts from previous side-projects including the SAAS template I've open-sourced some months ago https://github.com/gmpetrov/ultimate-saas-ts

Just want to share the side project I've built using the SAAS template I released a couple of months ago.

Hello 👋 Just want to share the side project I've built using the SAAS template I released a couple of months ago. Daftpage is a very simple landing page builder and blogging platform. With the right balance between simplicity and customization, you can ship very effective landing pages in minutes! It's perfect for:

Facebook auth has been added to the template

Btw this tool was built with the utlimate saas template i open-sourced some months ago https://github.com/gmpetrov/ultimate-saas-ts/tree/firebase-authentication

End-to-end typing with TypeGraphql + Graphql code generator

Source: https://github.com/gmpetrov/ultimate-saas-ts/tree/firebase-a...

Demo: https://utlimate-saas-firebase-ts.vercel.app

Source: https://github.com/gmpetrov/ultimate-saas-ts/tree/firebase-authentication

cross-env

or if we care about cross-platform compatibility (i.e. Windows support), we can use cross-env (which I also recommend to install as a dev dependency):

i like to use dotenv-flow and dynamically load it into node process. it's framework agnostic and can be combined with vaious other strategies, like explicitly set NODE_ENV with cross-env. all you need is the right command in your package.json, see a sample here.

Cross-env runs scripts that set and use environment variables across various platforms.

You will also need to disable the url-loader in your Docusaurus build which transforms images into base64 strings, as this will conflict with the plugin. There isn't a first class way to do this in Docusaurus at present. However by setting the environment variable WEBPACK_URL_LOADER_LIMIT to 0 you can disable it. You can see an implementation example in this pull request. It amounts to adding the cross-env package and then adding the following to your package.json:

Using the cross-env library, you'll tell the React Testing Library to skip auto cleanup after each test. More info and ways to configure here: Skipping Auto Cleanup. Now your configuration is enough to start writing tests, let's get started.

Now we need to load the files during the bootup. Windows environments sometimes face issues with loading the environments. To take care of that, let's install a package named cross-env

build; sets and enviroment valiable of NODE_ENV=production using cross-env lib and builds the production bundle, minified and without source-maps as set in the webpack.config.js file.

I'd suggest the cross-env NPM package which is used a lot (4M downlaods/week). Then you can just change it to the following:

Debugging Cypress tests using Visual Studio Code was possible earlier but with the latest version of Cypress, there is no direct way to do so. Even with the latest version of Cypress, a workaround was possible using Debugger for Chrome – a Visual Studio Code Extension and cross-env npm package. However, the Debugger for Chrome Extension for Visual Studio Code is deprecated and the cross-env npm package has gone into maintenance mode.