<p>Assuming all the other work regarding the package creation is done. To publish you have to do the following steps.</p><h2>Guide</h2><ul><li>update package.json with version</li><li>commit final changes</li><li>git tag -a v0.0.1 -m "stable 0.0.1"</li><li>git push origin --tags</li><li>vsce package</li><li>vsce publish</li></ul><h2>Install vsce if required.</h2><pre class="ql-syntax" spellcheck="false"><span class="hljs-built_in">npm</span> install -g vsce
</pre><h2>Generating Personal Token</h2><p>First time publishing will require the personal token for your market place. You can get it generated by following the steps <a href="https://code.visualstudio.com/api/working-with-extensions/publishing-extension" rel="noopener noreferrer">from here.</a></p>

How to publish vscode extension.

Assuming all the other work regarding the package creation is done. To publish you have to do the following steps.

<h2>What is laravel pint</h2><p>as in the defination by the official repository,</p><blockquote>Laravel Pint is an opinionated PHP code style fixer for minimalists. Pint is built on top of PHP-CS-Fixer and makes it simple to ensure that your code style stays clean and consistent.</blockquote><blockquote>-- laravel/pint</blockquote><p>and as per me, <strong>Pint is the so far most sophisticated code formatter i have ever user in the reference of PHP. </strong>You can find more details about <a href="https://github.com/laravel/pint" rel="noopener noreferrer">laravel/pint here</a>. </p><h2>Installation</h2><pre class="ql-syntax" spellcheck="false">composer <span class="hljs-built_in">require</span> laravel/pint --dev
</pre><h2>General Usage</h2><p>to use the pint binary all you have to do is run the following command in the root of you laravel project.</p><pre class="ql-syntax" spellcheck="false">./vendor/bin/pint
</pre><h2>Configuration</h2><p>The default setup of laravel pint does not require any configuration and as per the official docs, it for <a href="https://www.php-fig.org/psr/psr-12/" rel="noopener noreferrer">PSR-12 Style Guide</a>. Still if you are unhappy with some default rules you can change then by creating a<code> <strong>pint.json in root of your project</strong></code><strong>, </strong>and adding the preset to it.</p><p>Currently the following preset are supported</p><ol><li>psr12</li><li>laravel</li><li>symfony</li></ol><p>Since Pint is based on <strong>PHP-CS-Fixer the configuration rules can be found </strong><a href="https://mlocati.github.io/php-cs-fixer-configurator/#version:3.8" rel="noopener noreferrer"><strong>here</strong></a>.</p><h3>Sample pint.json</h3><pre class="ql-syntax" spellcheck="false">{
    <span class="hljs-attr">"preset"</span>: <span class="hljs-string">"symfony"</span>,
    <span class="hljs-attr">"rules"</span>: {
        <span class="hljs-attr">"concat_space"</span>: {
            <span class="hljs-attr">"spacing"</span>: <span class="hljs-string">"one"</span>
        }
    }
}
</pre><h2>Binding laravel pint with VS Code</h2><p>So far we are good to use laravel/pint, but opening terminal and running a binary everytime you need to format id one hell of a job. To reduce that effort we will bind laravel/pint with our VS Code with the help of <strong>VS Code Task</strong></p><h2>Creating VS Code task for laravel pint </h2><ol><li>To create a task create a <code>.vscode directory in root of you project</code>, if you don't have one.</li><li>Add a <code>new file named as tasks.json</code> to .vscode directory</li><li>add the following content to the new created file</li></ol><pre class="ql-syntax" spellcheck="false">{
    <span class="hljs-attr">"version"</span>: <span class="hljs-string">"2.0.0"</span>,
    <span class="hljs-attr">"tasks"</span>: [
        {
            <span class="hljs-attr">"label"</span>: <span class="hljs-string">"Pint Formatter"</span>,
            <span class="hljs-attr">"type"</span>: <span class="hljs-string">"shell"</span>,
            <span class="hljs-attr">"command"</span>: <span class="hljs-string">"./vendor/bin/pint"</span>,
            <span class="hljs-attr">"problemMatcher"</span>: [],
            <span class="hljs-attr">"presentation"</span>: {
                <span class="hljs-attr">"reveal"</span>: <span class="hljs-string">"silent"</span>
            },
            <span class="hljs-attr">"group"</span>: {
                <span class="hljs-attr">"kind"</span>: <span class="hljs-string">"build"</span>,
                <span class="hljs-attr">"isDefault"</span>: <span class="hljs-literal">true</span>
            }
        }
    ]
}
</pre><p>You can run this task directly from the <code>Tremial -&gt; Run Tasks</code> from the navigation, but will do it a bit more simpler.</p><h2>Adding KeyBinding (Keyboard Shortcut) to Run laravel pint</h2><ol><li>Open Keyboard shortcut panel, either from <code>file -&gt; preferences -&gt; keyboard Shortcuts</code> or <code>Ctrl+k Ctrl+s</code></li><li>Ones open click on the file icon on the top to open the json file of the keyboard shortcuts.</li><li>Ones open add the following lines to the file.</li></ol><pre class="ql-syntax" spellcheck="false">[
  {
    <span class="hljs-attr">"key"</span>: <span class="hljs-string">"ctrl+shift+l"</span>,
    <span class="hljs-attr">"command"</span>: <span class="hljs-string">"workbench.action.tasks.runTask"</span>,
    <span class="hljs-attr">"args"</span>: <span class="hljs-string">"Pint Formatter"</span>
  }
]
</pre><p>Now all you have to do is hit <code>Ctrl + Shift + l</code> and your laravel project will formatted with laravel pint.</p><h2>The Extension</h2><p>If  you are more driven toward the extension approach you can get the above integration by using the following extension.</p><h3><a href="https://marketplace.visualstudio.com/items?itemName=msamgan.laravel-pint-vscode" rel="noopener noreferrer">Vscode Laravel Pint Extension</a></h3><h3><a href="https://github.com/msamgan/vscode-larapint" rel="noopener noreferrer">Show Some Support by staring the repo</a></h3><h3><a href="https://marketplace.visualstudio.com/items?itemName=msamgan.laravel-pint-vscode" rel="noopener noreferrer">  </a></h3><h2>Conclusion</h2><p>I have been using the unsatisfactory formatters from a long time. All of them have one thing but lack other. Laravel Pint is one who has it all, combining it with vscode is like proving you laravel project a super power.</p><p>Feel free to pick your brain in comments.</p>

I have been using the unsatisfactory formatters from a long time. All of them have one thing but lack other. Laravel Pint is one who has it all, combining it with vscode is like proving you laravel project a super power.

How to Add Laravel Pint to VS Code Formatter

<p>NO, this is not another list of same old same old list of extensions.</p><p>VS Code is one of the most used editor of choice by a great number of developers. Here is a list of some extensions which I personally  use in my day to day development work and hope this will make you life a bit more easier.</p><p>Have a look</p><ol><li><a href="https://marketplace.visualstudio.com/items?itemName=usernamehw.errorlens" rel="noopener noreferrer">Error Lens</a></li><li><a href="https://marketplace.visualstudio.com/items?itemName=GitHub.copilot" rel="noopener noreferrer">GitHub Copilot</a></li><li><a href="https://marketplace.visualstudio.com/items?itemName=kruemelkatze.vscode-dashboard" rel="noopener noreferrer">Project Dashboard</a></li><li><a href="https://marketplace.visualstudio.com/items?itemName=pcsoftware.readable" rel="noopener noreferrer">Readable - AI Generated Comments</a></li><li><a href="https://marketplace.visualstudio.com/items?itemName=mutantdino.resourcemonitor" rel="noopener noreferrer">Resource Monitor</a></li><li><a href="https://marketplace.visualstudio.com/items?itemName=SonarSource.sonarlint-vscode" rel="noopener noreferrer">SonarLint</a></li><li><a href="https://marketplace.visualstudio.com/items?itemName=Gruntfuggly.todo-tree" rel="noopener noreferrer">Todo Tree</a></li><li><a href="https://marketplace.visualstudio.com/items?itemName=ChakrounAnas.turbo-console-log" rel="noopener noreferrer">Turbo Console Log</a></li><li><a href="https://marketplace.visualstudio.com/items?itemName=pflannery.vscode-versionlens" rel="noopener noreferrer">Version Lens</a></li><li><a href="https://marketplace.visualstudio.com/items?itemName=brapifra.phpserver" rel="noopener noreferrer">PHP Server</a></li><li><a href="https://marketplace.visualstudio.com/items?itemName=DavidAnson.vscode-markdownlint" rel="noopener noreferrer">markdownlint</a></li></ol><p>You can find the details for the above on there detail page.</p><p>Hope these comes handy to you too... </p><p><br></p>

NO, this is not another list of same old same old list of extensions.

How to publish vscode extension.

Table of Content

Guide

Install vsce if required.

Generating Personal Token

Guide

Install vsce if required.

Generating Personal Token