Steve Lee SteveALee

## gist:a9f838b79639949ac879
<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
    <PropertyGroup>
        <Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration>
        <SchemaVersion>2.0</SchemaVersion>
        <ProjectGuid>{1bf69820-c08a-4207-8084-5f6b180e52ff}</ProjectGuid>
        <ProjectHome />
        <ProjectView>ShowAllFiles</ProjectView>
        <StartupFile>index.js</StartupFile>
        <WorkingDirectory>.</WorkingDirectory>

## gist:4bd828882f2027f8878eb9ef856f7f60
<!DOCTYPE html>
<html lang="en">
	<style>
		body {
			margin: 1px;
		}

		#main {
			display: flex;
			flex-direction: column;

## gist:0e78dff6040780720093a14ce3a6f0ba

      
              1 file
            
          
              1 fork
            
          
              0 comments
            
          
              0 stars
            
          
                SteveALee
                / gist:0e78dff6040780720093a14ce3a6f0ba
            
            
              Last active
              September 16, 2021 05:12
            
              
                Have browsers update when editing 11ty config file
              
          
      View gist:0e78dff6040780720093a14ce3a6f0ba
  
      
    By default 11ty devmode uses browsersync to reload webbrowsers whenever it regenerates pages to _site.
It does this automatically when template files change.
However, the .eleventy.js file is only loaded when 11ty starts so if you edit shortcodes (say) you need to stop and restart 11ty.
The solution is to use nodemon to restart 11ty automatically when the config file changes.
But then you need to use browser F5 to refresh. The solution to that is to get browsersync to reload the browsers
To achieve that, the 11ty browsersync config option allows you to define a callback when browsersync is ready and you can add a browser reload call there.
Here's example code from music-practice-tools

  
## README.md

      
              2 files
            
          
              2 forks
            
          
              278 comments
            
          
              19 stars
            
          
                SteveALee
                / README.md
            
            
              Last active
              June 4, 2023 18:47
            
              
                Build audacity with ASIO support on Windows
              
          
      View README.md
  
      
    Build your own Audacity for Windows with ASIO driver support
Due to licensing restrictions the Audacity team cannot provide a prebuilt version with Windows ASIO driver support. But with this guide and script you can easily build your own Audacity 3.3.2.
Drivers are the glue between an audio program like Audacity and external hardware like a mixer or sound interface. The drivers usually used on Windows have limitations which can be overcome if you have ASIO drivers for your hardware. Specifically, low latency (delay) and multi channel support are available with ASIO drivers.
The Audacity program is the "go to" solution for many audio recording and editing tasks. However, unlike many more advanced DAWs, it doesn't support Windows ASIO drivers "out of the box". Fortunately, Audiacity's standard MME support is fine for most uses. That said, common reasons for needing ASIO include using digital audio or music equipment that only comes with ASIO drivers, such as Behringer mixe
	<?xml version="1.0" encoding="utf-8"?>
	<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
	<PropertyGroup>
	<Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration>
	<SchemaVersion>2.0</SchemaVersion>
	<ProjectGuid>{1bf69820-c08a-4207-8084-5f6b180e52ff}</ProjectGuid>
	<ProjectHome />
	<ProjectView>ShowAllFiles</ProjectView>
	<StartupFile>index.js</StartupFile>
	<WorkingDirectory>.</WorkingDirectory>
	<!DOCTYPE html>
	<html lang="en">
	<style>
	body {
	margin: 1px;
	}

	#main {
	display: flex;
	flex-direction: column;