-
### Self-service
- [ ] I'd be willing to implement a fix
### Describe the bug
Yarn pnp can't load synckit worker hence prettier plugin fails to run.
Why do I file this against yarn? Everything wo…
-
### Steps to reproduce
Create Vue 3 project:
```
yarn create farm myapp --template vue3
cd myapp
yarn
yarn add --dev vite # See issue 1420
yarn start # Works
```
Upgrade to modern yarn ve…
-
## 🎯 Aim of the feature
The objective is to provide information regarding necessary actions, such as possible upgrades, for PnP packages installed in a project.
Here are the packages that might…
-
### Reporting an Issue or Missing Feature
Get-PnPUserProfileProperty returning unexpected results in Runbook
### Expected behavior
Expecting a User Profile Properties PowerShell Object
### Ac…
-
### pnpm version:
6.25.1
### Code to reproduce the issue:
package.json:
```json
{
"dependencies": {
"@pnp/common": "2.0.5",
"@pnp/odata": "2.0.5",
"@pnp/sp-cli…
-
We are invoking starterkit v2 template and as per the requirements, we have the below pnp.powershell modules installed.
Name Version
---- -------
PnP.PowerShell 2.2.0
PnP.Pow…
-
## Category
- [x] Bug
## Describe the bug
Getting below error when trying to run the command.
Command: Invoke-PnPTenantTemplate -Path starterkit.pnp -Parameters @{"PORTALURL"="/sites/kitv3…
-
Hear me out. GPU Names reported by the driver is not the best way. We have to sanitize and each new graphics card can change it all, and some have extra stuff on their name such as MaxQ/8GB/SUPER.
…
-
I'm trying to use Vitest and I'm running into an issue with Yarn PnP:
> .pnp.cjs:101340 Uncaught Error: local-pkg tried to access vite, but it isn't declared in its dependencies; this makes the req…
-
## 🚀 Feature Proposal
Yarn Berry introduces the concept of a virtual package, whereby a source file may appear to Jest under a name different than the "real path". This happens when install…