Explore >> Select a destination
|
You are here 
|
vite.dev | ||
| | | | |
patak.dev
|
|
| | | | | [AI summary] The text provides an extensive overview of the Vite ecosystem, highlighting its integration with various frameworks, tools, and plugins. It discusses how Vite's fast development server, HMR, and optimized bundling have made it popular among developers. The post also mentions community contributions, templates, and tools like Tailwind CSS, UnoCSS, and StackBlitz, emphasizing the ecosystem's growth and the collaborative efforts of the community. | |
| | | | |
blog.stackblitz.com
|
|
| | | | | Today we're excited to announce our latest partner with StackBlitz WebContainers - **Shopify**! | |
| | | | |
vitejs.dev
|
|
| | | | | ||
| | | | |
vlad.website
|
|
| | | Sometimes, you want to add some code to test something out, but you definitely want to make sure you don't git commit it. Of course, you should always check the output of git diff before you make a commit (you do, right?), but if you have a lot of changes things can slip through the cracks. A solution is to write a comment containing a string such as "nocheckin": function do_stuff() { printf("hello!!! testing!!!\n"); // nocheckin call_important_thing(); call_other_thing(); } Then, you need to set git up such that it refuses to make a commit if it detects the "nocheckin" string anywhere in your changed files. Here's how to do it. | ||
