If you're OK in having a node-esm
executable, please consider this solution.
#!/usr/bin/env sh
# the /usr/local/bin/node-esm executable
input_file=$1
shift
exec node --input-type=module - $@ <$input_file
import android.text.SpannableStringBuilder; | |
import android.text.Spanned; | |
import android.text.TextPaint; | |
import android.text.method.LinkMovementMethod; | |
import android.text.style.ClickableSpan; | |
import android.view.View; | |
import android.widget.TextView; | |
import java.util.ArrayList; | |
import java.util.regex.Matcher; |
protected ResponseEntity<Resource<List<Attachment>>> patchMultipartApiV1_Treatments_TID(final String aTID, | |
final Treatment aTreatment, | |
final boolean keepLock, | |
final MultipartFile... aMultipartFiles) throws IOException { | |
final MultiValueMap<String, Object> theMultipartRequest = new LinkedMultiValueMap<>(); | |
// creating an HttpEntity for the JSON part: | |
final HttpHeaders theJsonHeader = new HttpHeaders(); | |
theJsonHeader.setContentType(MediaType.APPLICATION_JSON); |
import org.yaml.snakeyaml.DumperOptions | |
import org.yaml.snakeyaml.Yaml | |
buildscript{ | |
ext{ | |
springBootVersion = '1.5.7.RELEASE' | |
} | |
repositories{ | |
mavenCentral() | |
} |
If you're OK in having a node-esm
executable, please consider this solution.
#!/usr/bin/env sh
# the /usr/local/bin/node-esm executable
input_file=$1
shift
exec node --input-type=module - $@ <$input_file
I'm a Rust newbie, and one of the things that I've found frustrating is that the default docker build
experience is extremely slow. As it downloads crates, then dependencies, then finally my app - I often get distracted, start doing something else, then come back several minutes later and forget what I was doing
Recently, I had the idea to make it a little better by combining multistage builds with some of the amazing features from BuildKit. Specifically, cache mounts, which let a build container cache directories for compilers & package managers. Here's a quick annotated before & after from a real app I encountered.
This is a standard enough multistage Dockerfile. Nothing seemingly terrible or great here - just a normal build stage, and a smaller runtime stage.