setup-node
vscodium
setup-node | vscodium | |
---|---|---|
24 | 535 | |
3,620 | 23,774 | |
3.4% | 1.4% | |
7.2 | 9.5 | |
7 days ago | 13 days ago | |
TypeScript | Shell | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
setup-node
-
CI/CI deploy a static website to AWS S3 bucket through Github Actions
Setup environment with Nodejs and install dependencies with npm install, with Github Actions setup Node
-
VSCodium β Libre Open Source Software Binaries of VS Code
No, PR review isn't the only thing that prevents these from being updated. In the yml it's set to a release branch. So it isn't especially fallible.
https://github.com/actions/setup-node/tree/releases/v2
- Disable Annotations in Github Actions
-
A guide to using act with GitHub Actions
β getting-started-with-act git:(master) act -j build WARN β You are using Apple M1 chip and you have not specified container architecture, you might encounter issues while running act. If so, try running it with '--container-architecture linux/amd64'. β [Node.js CI/build] π Start image=node:16-buster-slim [Node.js CI/build] π³ docker pull image=node:16-buster-slim platform= username= forcePull=false [Node.js CI/build] π³ docker create image=node:16-buster-slim platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] [Node.js CI/build] π³ docker run image=node:16-buster-slim platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] [Node.js CI/build] β git clone 'https://github.com/actions/setup-node' # ref=v3 [Node.js CI/build] β git clone 'https://github.com/actions/cache' # ref=v3 [Node.js CI/build] β git clone 'https://github.com/actions/upload-artifact' # ref=v3 [Node.js CI/build] β Run Main actions/checkout@v3 [Node.js CI/build] π³ docker cp src=/Users/andrewevans/Documents/projects/getting-started-with-act/. dst=/Users/andrewevans/Documents/projects/getting-started-with-act [Node.js CI/build] β Success - Main actions/checkout@v3 [Node.js CI/build] β Run Main Use Node.js 16.x [Node.js CI/build] π³ docker cp src=/Users/andrewevans/.cache/act/actions-setup-node@v3/ dst=/var/run/act/actions/actions-setup-node@v3/ [Node.js CI/build] π³ docker exec cmd=[node /var/run/act/actions/actions-setup-node@v3/dist/setup/index.js] user= workdir= [Node.js CI/build] π¬ ::debug::isExplicit: [Node.js CI/build] π¬ ::debug::explicit? false
-
Cheap Gatsby/Netlify-style Hosting?
steps: # Check out the current repository code - uses: actions/checkout@v3 # 3. https://github.com/actions/setup-node#usage - name: Setup node and build Gatsby uses: actions/setup-node@v1 with: node-version: '16.x' cache: 'npm' - run: npm install # This triggers `gatsby build` script in "package.json" - run: npm run build # 4. Deploy the gatsby build to Netlify - name: Deploy to netlify uses: netlify/actions/cli@master env: NETLIFY_AUTH_TOKEN: ${{ secrets.NETLIFY_AUTH_TOKEN }} NETLIFY_SITE_ID: ${{ secrets.NETLIFY_SITE_ID }} with: # 5. "gatsby build" creates "public" folder, which is what we are deploying args: deploy --dir=public --prod secrets: '["NETLIFY_AUTH_TOKEN", "NETLIFY_SITE_ID"]'
-
5 Ways to make development with GitHub Actions more efficient
If you see repeated build or preparation steps that do not change when your codebase changes, look into caching the results. Here is a straightforward guide to caching, but also be aware caching is built into a lot of marketplace actions anyway, e.g. actions/setup-node can cache npm dependencies.
-
Top 10 GitHub Actions You Should Use to set up your CI/CD Pipeline
The most popular ones are Node.js, Python, Java JDK, Go, .Net Core SDK.
-
The strongest principle of the blog's growth lies in the human choice to deploy it
diff --git a/.github/workflows/gh-pages.yaml b/.github/workflows/gh-pages.yaml index 401fd33..3ddf6dd 100644 --- a/.github/workflows/gh-pages.yaml +++ b/.github/workflows/gh-pages.yaml @@ -11,42 +11,48 @@ on: jobs: deploy: - runs-on: ubuntu-20.04 + runs-on: ubuntu-22.04 + # Ensure that only a single job or workflow + # https://docs.github.com/en/actions/using-jobs/using-concurrency concurrency: + # workflow - The name of the workflow. + # ref - The branch or tag ref that triggered the workflow run. group: ${{ github.workflow }}-${{ github.ref }} steps: - uses: actions/checkout@v3 with: - submodules: true # Fetch Hugo themes (true OR recursive) fetch-depth: 0 # Fetch all history for .GitInfo and .Lastmod + # https://github.com/peaceiris/actions-hugo - name: Setup Hugo uses: peaceiris/actions-hugo@v2 with: - hugo-version: '0.91.2' - # extended: true + hugo-version: '0.101.0' + # https://github.com/actions/setup-node - name: Setup Node uses: actions/setup-node@v3 with: - node-version: '14' - - - name: Cache dependencies - uses: actions/cache@v2 - with: - path: ~/.npm - key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }} - restore-keys: | - ${{ runner.os }}-node- - - - run: npm ci + node-version: '18.7.0' + cache: npm + # The action defaults to search for the dependency file (package-lock.json, + # npm-shrinkwrap.json or yarn.lock) in the repository root, and uses its + # hash as a part of the cache key. + # https://github.com/actions/setup-node/blob/main/docs/advanced-usage.md#caching-packages-data + cache-dependency-path: ./blog/package-lock.json + + - name: Install npm dependencies + working-directory: ./blog/ + run: npm ci - name: Build - run: hugo --minify + working-directory: ./blog/ + run: npm run build + # https://github.com/peaceiris/actions-gh-pages - name: Deploy uses: peaceiris/actions-gh-pages@v3 if: ${{ github.ref == 'refs/heads/main' }} with: github_token: ${{ secrets.GITHUB_TOKEN }} - publish_dir: ./public + publish_dir: ./blog/src/public
-
How Fastly manages its software with GitHub Actions
Well, letβs consider the scenario we had with the DevHub. We were using the third-party action setup-node to install and configure the Node.js programming language. This action lets you specify the node version to install but it canβt be a dynamically acquired value. You either have to hardcode it or interpolate the value.
-
GitHub Actions Is Down
This is hitting workflows that use caching [1][2].
- [1] https://github.com/actions/setup-node/issues/516
- [2] https://github.com/actions/cache/issues/820
As of now (11:28 UTC) the status page has been updated.
https://www.githubstatus.com
vscodium
-
What is VSCodium ? Better than VS code ?
https://github.com/VSCodium/vscodium/releases
-
DHH: VSCode and WSL makes Windows awesome for web development
Well, my Ubuntu with https://vscodium.com/ is certainly much better for web development than fucking windows. I boot windows only for gaming. I detest their spyware adware OS. Furthermore, I detest "99% open source with 1% bullshit on top of it" products like Chrome and VScode. I will never use the official versions of such programs. I use Brave to use Blink/Chromium, it also has the benefit of not suffering from the v3 manifest bullshit they pulled to attack and weaken Adblockers.
WSL is cool and all, but why deal with all the quirks and issue that come with it, why lorn how it works and all the limitations ... when you can just have it all natively the way it was invented and supposed to work?
-
Phind-70B: Closing the code quality gap with GPT-4 Turbo while running 4x faster
I wonder if [VSCodium](https://vscodium.com/) suffers from same issues
-
JetBrains' unremovable AI assistant meets irresistible outcry
Seems like you still lose the Python plugin and remote extensions? Missing the wsl one is pretty rough. If youβre comfortable with vim (or want to be) I canβt recommend neovim enough.
https://github.com/VSCodium/vscodium/wiki/Extensions-Compati...
-
VSCode is no longer compatible with Ubuntu 18.04, here's what you can do
Use Codium. https://vscodium.com/
Anything Microsoft-branded will shoot you in the face sooner or later.
-
15 open-source tools to elevate your software design workflow
No matter what project you're developing on, at some point you'll give VSCode (or its open source version) a try. You can use it to develop in a dedicated dev-environment or debug integration scenarios.
-
The Loneliness of the Mid-Level Vimmer
Hello, and welcome to vscodium:
https://github.com/VSCodium/vscodium
-
Raylib Library For Video Games Programming as Senior Developer
So Raylib library could be your best option. Let's code, just open your text editor like vim or VSCodium in your Windows, Linux or Mac computer and let's build our indie game with Raylib library, no extra dependencies are needed.
-
What's the best model for coding with VS Code?
From my own experience Debian Bookworm with XFCE + VScodium is a winner on the X220.
-
XCurl
To be fair, there is vscodium[1] which is only a few letters off vscode:
https://vscodium.com/
What are some alternatives?
yarn - The 1.x line is frozen - features and bugfixes now happen on https://github.com/yarnpkg/berry
Code-Server - VS Code in the browser
setup-buildx-action - GitHub Action to set up Docker Buildx
Visual Studio Code - Visual Studio Code
upload-artifact
vscode-cpptools - Official repository for the Microsoft C/C++ extension for VS Code.
checkout - Action for checking out a repo
Visual Studio Code - Public documentation for Visual Studio Code
actions-gh-pages - GitHub Actions for GitHub Pages π Deploy static files and publish your site easily. Static-Site-Generators-friendly.
pylance-release - Documentation and issues for Pylance
act - Run your GitHub Actions locally π
theia - Eclipse Theia is a cloud & desktop IDE framework implemented in TypeScript.