If you have a large number of Angular projects and defining individual build commands for each project in the package.json file becomes unwieldy, you can consider using a different approach to organize your build commands. Here are a few suggestions:
- Create a separate configuration file: Instead of cluttering your package.json file with multiple build commands, you can create a separate configuration file (e.g., angular-projects.json) to store the build configurations for each project. In this file, you can define an array of objects, where each object represents a project and its corresponding build command.
Example angular-projects.json:
[
{
"name": "ProjectA",
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
import { useStateWithCallback } from './useStateWithCallback'; | |
function MyComponent() { | |
const [count, setCount] = useStateWithCallback(0, (value) => { | |
console.log(`Count updated: ${value}`); | |
}); | |
function increment() { | |
setCount(count + 1, () => { | |
console.log(`Count incremented: ${count + 1}`); |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
echo "QuickbootFileBacked = off" >> ~/.android/advancedFeatures.ini |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
yarn install -std=c++17 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/zsh | |
# A simple script with a function... | |
mexec() | |
{ | |
export THE_COMMAND=$@ | |
find . -type d -maxdepth 1 -mindepth 1 -print0 | xargs -0 -I{} zsh -c 'cd "{}" && echo "*\033[1;32mstart {} start\033[0m*" && echo "$('$THE_COMMAND')" && echo -e "*\033[1;93mend {} end\033[0m*\n"' | |
} | |
mexec ls -al |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
const response = await axios.get( | |
`http://gateway.marvel.com/v1/public/comics?ts=${timeStamp}&apikey=${apiKey}&hash=${md5}&limit=20&offset=${ | |
(page - 1) * 20 | |
}` | |
); |
- Download the latest zsh package: https://packages.msys2.org/package/zsh?repo=msys&variant=x86_64
Example:
zsh-5.7.1-1-x86_64.pkg.tar.xz
NewerOlder