#yeoman — Public Fediverse posts on home.social

PugJesus @[email protected] · 2026-05-20 · 01:51 UTC

The sturdy Yeoman at Crecy! (Gambargin)

https://piefed.social/c/historymemes/p/2075356/the-sturdy-yeoman-at-crecy-gambargin

#history #uk #england #meme #military #longbow

PugJesus @[email protected] · 2026-05-20 · 01:51 UTC

The sturdy Yeoman at Crecy! (Gambargin)

#history #uk #england #meme #military #longbow

PugJesus @[email protected] · 2026-05-20 · 01:51 UTC

The sturdy Yeoman at Crecy! (Gambargin)

https://piefed.social/c/historymemes/p/2075356/the-sturdy-yeoman-at-crecy-gambargin

#history #uk #england #meme #military #longbow

PugJesus @[email protected] · 2026-05-20 · 01:51 UTC

The sturdy Yeoman at Crecy! (Gambargin)

https://piefed.social/c/historymemes/p/2075356/the-sturdy-yeoman-at-crecy-gambargin

#yeoman #crecy #grimdank #gambargin #battletech #mechwarrior

PugJesus @[email protected] · 2026-05-20 · 01:51 UTC

The sturdy Yeoman at Crecy! (Gambargin)

https://piefed.social/c/historymemes/p/2075356/the-sturdy-yeoman-at-crecy-gambargin

#history #uk #england #meme #military #longbow

PugJesus @[email protected] · 2026-05-20 · 01:50 UTC

The sturdy Yeoman at Crecy! (Gambargin)

https://piefed.social/c/grimdank/p/2075355/the-sturdy-yeoman-at-crecy-gambargin

#history #uk #england #meme #military #longbow

PugJesus @[email protected] · 2026-05-20 · 01:50 UTC

The sturdy Yeoman at Crecy! (Gambargin)

#history #uk #england #meme #military #longbow

PugJesus @[email protected] · 2026-05-20 · 01:50 UTC

The sturdy Yeoman at Crecy! (Gambargin)

#history #uk #england #meme #military #longbow

PugJesus @[email protected] · 2026-05-20 · 01:50 UTC

The sturdy Yeoman at Crecy! (Gambargin)

#yeoman #crecy #grimdank #gambargin #battletech #mechwarrior

PugJesus @[email protected] · 2026-05-20 · 01:50 UTC

The sturdy Yeoman at Crecy! (Gambargin)

#history #uk #england #meme #military #longbow

Bryan King @[email protected] · 2026-01-04 · 12:30 UTC

SPFx Deployment Demystified: Step-by-Step for Developers Who Mean Business

686 words, 4 minutes read time.

The world of SharePoint Framework (SPFx) development has come a long way since its inception, but for many developers, the process of deploying and managing these solutions remains shrouded in
mystery.

Introduction

As a developer, understanding SPFx deployment is crucial to delivering high-quality, scalable, and secure solutions. In this article, we’ll delve into the step-by-step process of deploying SPFx projects, covering the key considerations, technical nuances, and best practices that will help you master this essential skill.

Pre-Deployment Planning

Before embarking on your deployment journey, it’s essential to plan carefully. This involves understanding your target environment, identifying any dependencies or prerequisites, and choosing the right tools and resources for the job.

const manifest = require('./manifest.json');console.log(manifest);

Setting Up Your Environment

To deploy an SPFx solution, you’ll need to set up your development environment. This includes installing the necessary tools, such as Yeoman, gulp, and the SharePoint Framework CLI.

npm install -g @microsoft/generator-sharepointgulp new project

Building and Packaging Your Solution

Once you’ve set up your environment, it’s time to build and package your SPFx solution. This involves creating a package file (.sppkg) that contains all the necessary files and dependencies.

gulp package-solution

Deploying Your Solution

The deployment process itself is where things can get complex. You’ll need to consider factors such as security, permissions, and scalability. In this section, we’ll explore some best practices for deploying SPFx solutions in a production environment.

const deploy = require('@microsoft/sp-deployment-webpack');deploy(manifest, { env: 'prod' });

Post-Deployment Tasks

After deployment, there are several tasks to complete. These include configuring security settings, testing the solution, and monitoring performance.

const config = require('./config.json');console.log(config);

Best Practices and Patterns

Throughout this article, we’ve highlighted some key considerations for deploying SPFx solutions. However, there are many more best practices and patterns to explore. In this section, we’ll discuss some additional strategies for improving the overall quality and
reliability of your deployments.

Reflection / Challenge

What are some common pitfalls or challenges you’ve encountered when deploying SPFx solutions in the past?
How do you ensure that your solution is scalable and secure in a production environment?
Can you think of any additional tools or resources that would make the deployment process easier or more efficient?

Conclusion / Next Steps

Deploying SPFx solutions requires careful planning, attention to detail, and a deep understanding of the underlying technology. By following the steps outlined in this article, you’ll be well on your way to mastering this critical skill. However, there’s always more to learn, so we recommend exploring additional resources and best practices for continued growth and improvement.

Next Steps: Take some time to review the code examples and best practices outlined in this article. Experiment with different deployment scenarios and test your skills on a small project before tackling a larger solution. And don’t be afraid to ask questions or seek guidance from more experienced developers!

Call to Action

If this post sparked your creativity, don’t just scroll past. Join the community of makers and tinkerers—people turning ideas into reality with 3D printing. Subscribe for more 3D printing guides and projects, drop a
comment sharing what you’re printing, or reach out and tell me about your latest project. Let’s build together.

Sources

Disclaimer:

The views and opinions expressed in this post are solely those of the author. The information provided is based on personal research, experience, and understanding of the subject matter at the time of writing. Readers should consult relevant experts or authorities for specific guidance related to their unique situations.

Related Posts

Rate this:

#MicrosoftGeneratorSharepoint #azure #bestPractices #cloudSolutions #configJson #deployment #deploymentScript #devEnvironment #devops #environmentVariables #Gulp #gulpNewProject #gulpPackageSolution #gulpWebpack #JavaScript #management #manifestJson #microsoft365 #nodejs #npmInstall #npmUpdate #office365 #onPremisesDeployment #patterns #performanceMonitoring #productionEnvironment #reliability #scalability #security #securitySettings #sharepointAdministration #SharePointFramework #sharepointFrameworkCli #SharePointScalability #SharePointSecurity #softwareDevelopment #solutionPackage #SPFxDevelopment #sppkgFile #testing #WebDevelopment #webpackBundle #Yeoman

#microsoftgeneratorsharepoint #azure #bestpractices #cloudsolutions #configjson #deployment

Bryan King @[email protected] · 2026-01-04 · 12:30 UTC

SPFx Deployment Demystified: Step-by-Step for Developers Who Mean Business

686 words, 4 minutes read time.

The world of SharePoint Framework (SPFx) development has come a long way since its inception, but for many developers, the process of deploying and managing these solutions remains shrouded in
mystery.

Introduction

As a developer, understanding SPFx deployment is crucial to delivering high-quality, scalable, and secure solutions. In this article, we’ll delve into the step-by-step process of deploying SPFx projects, covering the key considerations, technical nuances, and best practices that will help you master this essential skill.

Pre-Deployment Planning

Before embarking on your deployment journey, it’s essential to plan carefully. This involves understanding your target environment, identifying any dependencies or prerequisites, and choosing the right tools and resources for the job.

const manifest = require('./manifest.json');console.log(manifest);

Setting Up Your Environment

To deploy an SPFx solution, you’ll need to set up your development environment. This includes installing the necessary tools, such as Yeoman, gulp, and the SharePoint Framework CLI.

npm install -g @microsoft/generator-sharepointgulp new project

Building and Packaging Your Solution

Once you’ve set up your environment, it’s time to build and package your SPFx solution. This involves creating a package file (.sppkg) that contains all the necessary files and dependencies.

gulp package-solution

Deploying Your Solution

The deployment process itself is where things can get complex. You’ll need to consider factors such as security, permissions, and scalability. In this section, we’ll explore some best practices for deploying SPFx solutions in a production environment.

const deploy = require('@microsoft/sp-deployment-webpack');deploy(manifest, { env: 'prod' });

Post-Deployment Tasks

After deployment, there are several tasks to complete. These include configuring security settings, testing the solution, and monitoring performance.

const config = require('./config.json');console.log(config);

Best Practices and Patterns

Throughout this article, we’ve highlighted some key considerations for deploying SPFx solutions. However, there are many more best practices and patterns to explore. In this section, we’ll discuss some additional strategies for improving the overall quality and
reliability of your deployments.

Reflection / Challenge

What are some common pitfalls or challenges you’ve encountered when deploying SPFx solutions in the past?
How do you ensure that your solution is scalable and secure in a production environment?
Can you think of any additional tools or resources that would make the deployment process easier or more efficient?

Conclusion / Next Steps

Deploying SPFx solutions requires careful planning, attention to detail, and a deep understanding of the underlying technology. By following the steps outlined in this article, you’ll be well on your way to mastering this critical skill. However, there’s always more to learn, so we recommend exploring additional resources and best practices for continued growth and improvement.

Next Steps: Take some time to review the code examples and best practices outlined in this article. Experiment with different deployment scenarios and test your skills on a small project before tackling a larger solution. And don’t be afraid to ask questions or seek guidance from more experienced developers!

Call to Action

If this post sparked your creativity, don’t just scroll past. Join the community of makers and tinkerers—people turning ideas into reality with 3D printing. Subscribe for more 3D printing guides and projects, drop a
comment sharing what you’re printing, or reach out and tell me about your latest project. Let’s build together.

Sources

Disclaimer:

The views and opinions expressed in this post are solely those of the author. The information provided is based on personal research, experience, and understanding of the subject matter at the time of writing. Readers should consult relevant experts or authorities for specific guidance related to their unique situations.

Related Posts

Rate this:

#MicrosoftGeneratorSharepoint #azure #bestPractices #cloudSolutions #configJson #deployment #deploymentScript #devEnvironment #devops #environmentVariables #Gulp #gulpNewProject #gulpPackageSolution #gulpWebpack #JavaScript #management #manifestJson #microsoft365 #nodejs #npmInstall #npmUpdate #office365 #onPremisesDeployment #patterns #performanceMonitoring #productionEnvironment #reliability #scalability #security #securitySettings #sharepointAdministration #SharePointFramework #sharepointFrameworkCli #SharePointScalability #SharePointSecurity #softwareDevelopment #solutionPackage #SPFxDevelopment #sppkgFile #testing #WebDevelopment #webpackBundle #Yeoman

#microsoftgeneratorsharepoint #azure #bestpractices #cloudsolutions #configjson #deployment

Bryan King @[email protected] · 2026-01-04 · 12:30 UTC

SPFx Deployment Demystified: Step-by-Step for Developers Who Mean Business

686 words, 4 minutes read time.

The world of SharePoint Framework (SPFx) development has come a long way since its inception, but for many developers, the process of deploying and managing these solutions remains shrouded in
mystery.

Introduction

As a developer, understanding SPFx deployment is crucial to delivering high-quality, scalable, and secure solutions. In this article, we’ll delve into the step-by-step process of deploying SPFx projects, covering the key considerations, technical nuances, and best practices that will help you master this essential skill.

Pre-Deployment Planning

Before embarking on your deployment journey, it’s essential to plan carefully. This involves understanding your target environment, identifying any dependencies or prerequisites, and choosing the right tools and resources for the job.

const manifest = require('./manifest.json');console.log(manifest);

Setting Up Your Environment

To deploy an SPFx solution, you’ll need to set up your development environment. This includes installing the necessary tools, such as Yeoman, gulp, and the SharePoint Framework CLI.

npm install -g @microsoft/generator-sharepointgulp new project

Building and Packaging Your Solution

Once you’ve set up your environment, it’s time to build and package your SPFx solution. This involves creating a package file (.sppkg) that contains all the necessary files and dependencies.

gulp package-solution

Deploying Your Solution

The deployment process itself is where things can get complex. You’ll need to consider factors such as security, permissions, and scalability. In this section, we’ll explore some best practices for deploying SPFx solutions in a production environment.

const deploy = require('@microsoft/sp-deployment-webpack');deploy(manifest, { env: 'prod' });

Post-Deployment Tasks

After deployment, there are several tasks to complete. These include configuring security settings, testing the solution, and monitoring performance.

const config = require('./config.json');console.log(config);

Best Practices and Patterns

Throughout this article, we’ve highlighted some key considerations for deploying SPFx solutions. However, there are many more best practices and patterns to explore. In this section, we’ll discuss some additional strategies for improving the overall quality and
reliability of your deployments.

Reflection / Challenge

What are some common pitfalls or challenges you’ve encountered when deploying SPFx solutions in the past?
How do you ensure that your solution is scalable and secure in a production environment?
Can you think of any additional tools or resources that would make the deployment process easier or more efficient?

Conclusion / Next Steps

Deploying SPFx solutions requires careful planning, attention to detail, and a deep understanding of the underlying technology. By following the steps outlined in this article, you’ll be well on your way to mastering this critical skill. However, there’s always more to learn, so we recommend exploring additional resources and best practices for continued growth and improvement.

Next Steps: Take some time to review the code examples and best practices outlined in this article. Experiment with different deployment scenarios and test your skills on a small project before tackling a larger solution. And don’t be afraid to ask questions or seek guidance from more experienced developers!

Call to Action

If this post sparked your creativity, don’t just scroll past. Join the community of makers and tinkerers—people turning ideas into reality with 3D printing. Subscribe for more 3D printing guides and projects, drop a
comment sharing what you’re printing, or reach out and tell me about your latest project. Let’s build together.

Sources

Disclaimer:

The views and opinions expressed in this post are solely those of the author. The information provided is based on personal research, experience, and understanding of the subject matter at the time of writing. Readers should consult relevant experts or authorities for specific guidance related to their unique situations.

Related Posts

Rate this:

#MicrosoftGeneratorSharepoint #azure #bestPractices #cloudSolutions #configJson #deployment #deploymentScript #devEnvironment #devops #environmentVariables #Gulp #gulpNewProject #gulpPackageSolution #gulpWebpack #JavaScript #management #manifestJson #microsoft365 #nodejs #npmInstall #npmUpdate #office365 #onPremisesDeployment #patterns #performanceMonitoring #productionEnvironment #reliability #scalability #security #securitySettings #sharepointAdministration #SharePointFramework #sharepointFrameworkCli #SharePointScalability #SharePointSecurity #softwareDevelopment #solutionPackage #SPFxDevelopment #sppkgFile #testing #WebDevelopment #webpackBundle #Yeoman

#microsoftgeneratorsharepoint #azure #bestpractices #cloudsolutions #configjson #deployment

Bryan King @[email protected] · 2026-01-04 · 12:30 UTC

SPFx Deployment Demystified: Step-by-Step for Developers Who Mean Business

686 words, 4 minutes read time.

The world of SharePoint Framework (SPFx) development has come a long way since its inception, but for many developers, the process of deploying and managing these solutions remains shrouded in
mystery.

Introduction

As a developer, understanding SPFx deployment is crucial to delivering high-quality, scalable, and secure solutions. In this article, we’ll delve into the step-by-step process of deploying SPFx projects, covering the key considerations, technical nuances, and best practices that will help you master this essential skill.

Pre-Deployment Planning

Before embarking on your deployment journey, it’s essential to plan carefully. This involves understanding your target environment, identifying any dependencies or prerequisites, and choosing the right tools and resources for the job.

const manifest = require('./manifest.json');console.log(manifest);

Setting Up Your Environment

To deploy an SPFx solution, you’ll need to set up your development environment. This includes installing the necessary tools, such as Yeoman, gulp, and the SharePoint Framework CLI.

npm install -g @microsoft/generator-sharepointgulp new project

Building and Packaging Your Solution

Once you’ve set up your environment, it’s time to build and package your SPFx solution. This involves creating a package file (.sppkg) that contains all the necessary files and dependencies.

gulp package-solution

Deploying Your Solution

The deployment process itself is where things can get complex. You’ll need to consider factors such as security, permissions, and scalability. In this section, we’ll explore some best practices for deploying SPFx solutions in a production environment.

const deploy = require('@microsoft/sp-deployment-webpack');deploy(manifest, { env: 'prod' });

Post-Deployment Tasks

After deployment, there are several tasks to complete. These include configuring security settings, testing the solution, and monitoring performance.

const config = require('./config.json');console.log(config);

Best Practices and Patterns

Throughout this article, we’ve highlighted some key considerations for deploying SPFx solutions. However, there are many more best practices and patterns to explore. In this section, we’ll discuss some additional strategies for improving the overall quality and
reliability of your deployments.

Reflection / Challenge

What are some common pitfalls or challenges you’ve encountered when deploying SPFx solutions in the past?
How do you ensure that your solution is scalable and secure in a production environment?
Can you think of any additional tools or resources that would make the deployment process easier or more efficient?

Conclusion / Next Steps

Deploying SPFx solutions requires careful planning, attention to detail, and a deep understanding of the underlying technology. By following the steps outlined in this article, you’ll be well on your way to mastering this critical skill. However, there’s always more to learn, so we recommend exploring additional resources and best practices for continued growth and improvement.

Next Steps: Take some time to review the code examples and best practices outlined in this article. Experiment with different deployment scenarios and test your skills on a small project before tackling a larger solution. And don’t be afraid to ask questions or seek guidance from more experienced developers!

Call to Action

If this post sparked your creativity, don’t just scroll past. Join the community of makers and tinkerers—people turning ideas into reality with 3D printing. Subscribe for more 3D printing guides and projects, drop a
comment sharing what you’re printing, or reach out and tell me about your latest project. Let’s build together.

Sources

Disclaimer:

The views and opinions expressed in this post are solely those of the author. The information provided is based on personal research, experience, and understanding of the subject matter at the time of writing. Readers should consult relevant experts or authorities for specific guidance related to their unique situations.

Related Posts

Rate this:

#MicrosoftGeneratorSharepoint #azure #bestPractices #cloudSolutions #configJson #deployment #deploymentScript #devEnvironment #devops #environmentVariables #Gulp #gulpNewProject #gulpPackageSolution #gulpWebpack #JavaScript #management #manifestJson #microsoft365 #nodejs #npmInstall #npmUpdate #office365 #onPremisesDeployment #patterns #performanceMonitoring #productionEnvironment #reliability #scalability #security #securitySettings #sharepointAdministration #SharePointFramework #sharepointFrameworkCli #SharePointScalability #SharePointSecurity #softwareDevelopment #solutionPackage #SPFxDevelopment #sppkgFile #testing #WebDevelopment #webpackBundle #Yeoman

#yeoman #webpackbundle #webdevelopment #testing #sppkgfile #spfxdevelopment

Bryan King @[email protected] · 2026-01-04 · 12:30 UTC

SPFx Deployment Demystified: Step-by-Step for Developers Who Mean Business

686 words, 4 minutes read time.

The world of SharePoint Framework (SPFx) development has come a long way since its inception, but for many developers, the process of deploying and managing these solutions remains shrouded in
mystery.

Introduction

As a developer, understanding SPFx deployment is crucial to delivering high-quality, scalable, and secure solutions. In this article, we’ll delve into the step-by-step process of deploying SPFx projects, covering the key considerations, technical nuances, and best practices that will help you master this essential skill.

Pre-Deployment Planning

Before embarking on your deployment journey, it’s essential to plan carefully. This involves understanding your target environment, identifying any dependencies or prerequisites, and choosing the right tools and resources for the job.

const manifest = require('./manifest.json');console.log(manifest);

Setting Up Your Environment

To deploy an SPFx solution, you’ll need to set up your development environment. This includes installing the necessary tools, such as Yeoman, gulp, and the SharePoint Framework CLI.

npm install -g @microsoft/generator-sharepointgulp new project

Building and Packaging Your Solution

Once you’ve set up your environment, it’s time to build and package your SPFx solution. This involves creating a package file (.sppkg) that contains all the necessary files and dependencies.

gulp package-solution

Deploying Your Solution

The deployment process itself is where things can get complex. You’ll need to consider factors such as security, permissions, and scalability. In this section, we’ll explore some best practices for deploying SPFx solutions in a production environment.

const deploy = require('@microsoft/sp-deployment-webpack');deploy(manifest, { env: 'prod' });

Post-Deployment Tasks

After deployment, there are several tasks to complete. These include configuring security settings, testing the solution, and monitoring performance.

const config = require('./config.json');console.log(config);

Best Practices and Patterns

Throughout this article, we’ve highlighted some key considerations for deploying SPFx solutions. However, there are many more best practices and patterns to explore. In this section, we’ll discuss some additional strategies for improving the overall quality and
reliability of your deployments.

Reflection / Challenge

What are some common pitfalls or challenges you’ve encountered when deploying SPFx solutions in the past?
How do you ensure that your solution is scalable and secure in a production environment?
Can you think of any additional tools or resources that would make the deployment process easier or more efficient?

Conclusion / Next Steps

Deploying SPFx solutions requires careful planning, attention to detail, and a deep understanding of the underlying technology. By following the steps outlined in this article, you’ll be well on your way to mastering this critical skill. However, there’s always more to learn, so we recommend exploring additional resources and best practices for continued growth and improvement.

Next Steps: Take some time to review the code examples and best practices outlined in this article. Experiment with different deployment scenarios and test your skills on a small project before tackling a larger solution. And don’t be afraid to ask questions or seek guidance from more experienced developers!

Call to Action

If this post sparked your creativity, don’t just scroll past. Join the community of makers and tinkerers—people turning ideas into reality with 3D printing. Subscribe for more 3D printing guides and projects, drop a
comment sharing what you’re printing, or reach out and tell me about your latest project. Let’s build together.

Sources

Disclaimer:

The views and opinions expressed in this post are solely those of the author. The information provided is based on personal research, experience, and understanding of the subject matter at the time of writing. Readers should consult relevant experts or authorities for specific guidance related to their unique situations.

Related Posts

Rate this:

#MicrosoftGeneratorSharepoint #azure #bestPractices #cloudSolutions #configJson #deployment #deploymentScript #devEnvironment #devops #environmentVariables #Gulp #gulpNewProject #gulpPackageSolution #gulpWebpack #JavaScript #management #manifestJson #microsoft365 #nodejs #npmInstall #npmUpdate #office365 #onPremisesDeployment #patterns #performanceMonitoring #productionEnvironment #reliability #scalability #security #securitySettings #sharepointAdministration #SharePointFramework #sharepointFrameworkCli #SharePointScalability #SharePointSecurity #softwareDevelopment #solutionPackage #SPFxDevelopment #sppkgFile #testing #WebDevelopment #webpackBundle #Yeoman

#microsoftgeneratorsharepoint #azure #bestpractices #cloudsolutions #configjson #deployment

Ulises Gascon @ulisesgascon · 2025-11-10 · 07:30 UTC

🔧 The latest issue of my #newsletter is out, number 009.

It dives into the new #Lodash governance and #security era, the #Yeoman cleanup and reboot, the #Expressjs 6 modernization journey… and much more 🔥

https://blog.ulisesgascon.com/newsletter-issue-9

#newsletter #lodash #security #yeoman #expressjs

Ulises Gascon @ulisesgascon · 2025-11-06 · 08:44 UTC

🎩 Big milestone for #yeoman!

We’ve completed a full #security review across the #Yeoman organization.

New policies, better automation, and stronger foundations for the next phase of the maintenance reboot process.

https://yeoman.io/blog/security-overhaul-2025

#yeoman #security

Ulises Gascon @ulisesgascon · 2025-11-03 · 12:15 UTC

I just sent my new Open Source Treats 🎃 newsletter to sponsors — packed with updates on #Lodash, #Yeoman & #Expressjs!

It’ll be public on my blog in a few days, but if you’d like early access and want to support my open source work:

👉 https://github.com/sponsors/UlisesGascon

#lodash #yeoman #expressjs

Ulises Gascon @ulisesgascon · 2025-11-01 · 20:04 UTC

Help us shape the future of #yeoman generator-webapp! 🎩

Deprecate or rebuild for 2025?

https://github.com/yeoman/generator-webapp/issues/790

#yeoman

Ulises Gascon @ulisesgascon · 2025-10-31 · 12:30 UTC

🚧 #yeoman Maintenance Reboot Update 🚧

As part of the ongoing #Yeoman maintenance reboot (https://github.com/yeoman/yeoman/issues/1779), we’ve archived and deprecated several legacy packages and repositories that are no longer actively maintained or relevant to modern workflows ✨

#yeoman

Stephen @[email protected] · 2025-09-12 · 04:07 UTC

I love #Remarkjs for creating #slides from #Markdown, that is, until I noticed the library is ~650 kB. So, then I went full on #FrugalComputing and looked for the smallest #HTML #presentation library...

That honour, AFAICT, goes to Mark Dalgleish's modular #Bespokejs. The #Yeoman generator failed for me, but with a little perseverance I hand coded a demo:
https://blog.harlow.net.nz/presentations/
that only required 8 kB of #Javascript. Remarkably, that's 1/80th of Remark.js!

👉 https://markdalgleish.com/projects/bespoke.js/

#remarkjs #slides #markdown #frugalcomputing #html #presentation

NorfolkGreg @[email protected] · 2025-06-15 · 18:27 UTC

Just realised! All the #dinghies on that Pontoon are #Yeoman (if not the drop keel variant the #kinsman

They used to be one of my favourite #halfdecker designs on the #Broads. Cheaper to maintain than the #traditional #wooden #classes found on the Broads, but I succumbed to the #SeaHawk which is a fabulous design for #solo #weekend #sailing
https://seahawk17.org.uk

#dinghies #yeoman #kinsman #halfdecker #broads #traditional

Ulises Gascon @ulisesgascon · 2025-04-30 · 13:11 UTC

🥹 May is almost here, and it's officially #MaintainerMonth 🚀

I’ve helped release #Express 5.1, ship key @nodejs updates, lead #OpenSource security work, and reboot #Yeoman.

If you believe in supporting #devTools, consider sponsoring ❤️

👉 https://github.com/sponsors/UlisesGascon

#maintainermonth #express #opensource #yeoman #devtools

Ulises Gascon @ulisesgascon · 2025-03-20 · 10:10 UTC

🎩 #yeoman Security Update 🔒

We're strengthening #security as part of our Maintenance Reboot Initiative!

✅ Now supporting responsible vulnerability reporting via #GitHub Security Advisories for faster & private fixes.

https://yeoman.io/blog/security-policy-update

#yeoman #security #github

Ulises Gascon @ulisesgascon · 2025-01-22 · 12:15 UTC

We're thrilled to unveil Yeoman's 2025 maintenance reboot! ✨

Fresh updates, enhanced tools, and a stronger community await.

Join us in shaping the future of #Yeoman:

https://yeoman.io/blog/maintenance-reboot

#yeoman

Ulises Gascon @ulisesgascon · 2025-01-21 · 16:22 UTC

🎉 Exciting news! #yeoman now has a dedicated Security Policy in place!

✨ We're committed to safeguarding our tools and the developer community.

🔒Explore how we're leveling up #OpenSource #security here:

https://github.com/yeoman/.github/security

#yeoman #opensource #security

Ulises Gascon @ulisesgascon · 2025-01-17 · 21:44 UTC

🚀 #yeoman is leveling up on #security!

New security plan includes:

🔒 Clear disclosure process
🔒 Threat modeling
🔒 #CVE reviews
🔒 #OSSFScorecard improvements

Help us build a safer #openSource future!
https://github.com/yeoman/.github/issues/1

#yeoman #security #cve #ossfscorecard #opensource

Ulises Gascon @[email protected] · 2025-01-17 · 21:44 UTC

🚀 #yeoman is leveling up on #security!

New security plan includes:

🔒 Clear disclosure process
🔒 Threat modeling
🔒 #CVE reviews
🔒 #OSSFScorecard improvements

Help us build a safer #openSource future!
https://github.com/yeoman/.github/issues/1

#yeoman #security #cve #ossfscorecard #opensource

Ulises Gascon @[email protected] · 2025-01-17 · 21:44 UTC

🚀 #yeoman is leveling up on #security!

New security plan includes:

🔒 Clear disclosure process
🔒 Threat modeling
🔒 #CVE reviews
🔒 #OSSFScorecard improvements

Help us build a safer #openSource future!
https://github.com/yeoman/.github/issues/1

#yeoman #security #cve #ossfscorecard #opensource

Ulises Gascon @[email protected] · 2025-01-17 · 21:44 UTC

🚀 #yeoman is leveling up on #security!

New security plan includes:

🔒 Clear disclosure process
🔒 Threat modeling
🔒 #CVE reviews
🔒 #OSSFScorecard improvements

Help us build a safer #openSource future!
https://github.com/yeoman/.github/issues/1

#opensource #ossfscorecard #cve #security #yeoman

Ulises Gascon @[email protected] · 2025-01-17 · 21:44 UTC

🚀 #yeoman is leveling up on #security!

New security plan includes:

🔒 Clear disclosure process
🔒 Threat modeling
🔒 #CVE reviews
🔒 #OSSFScorecard improvements

Help us build a safer #openSource future!
https://github.com/yeoman/.github/issues/1

#yeoman #security #cve #ossfscorecard #opensource

Ulises Gascon @ulisesgascon · 2025-01-14 · 13:43 UTC

✨ Dedicated to improving security, adding features, and supporting the community as an #Express TC member, #NodeJS collaborator, and #Yeoman maintainer. I maintain 180+ packages!

🙏 If your projects rely on them, please consider sponsoring: https://github.com/sponsors/UlisesGascon

#express #nodejs #yeoman

pezhore @[email protected] · 2024-08-02 · 13:50 UTC

Does anyone have a favorite project generator product for standardizing source code? I've tried Yeoman[^1], but it seems slow and I'm not great at #NodeJS.

I'd like to have something for my team to use to get some boilerplate #Terraform projects with standard naming, folder structure, etc - ideally with some customization based on user input at generation time.

[^1]: https://yeoman.io/

#DevOps #SourceCode #Automation #Yeoman

#nodejs #terraform #devops #sourcecode #automation #yeoman

NSIS @nsis · 2022-11-01 · 16:21 UTC

#github release: generator-nlf v0.2.0 https://github.com/idleberg/generator-nlf/releases #yeoman

#github #yeoman

NSIS @nsis · 2022-11-01 · 16:20 UTC

#github release: generator-nsis v0.9.0 https://github.com/idleberg/generator-nsis/releases #yeoman

#github #yeoman