[Tiny 6.1.0] "only in private projects"
See original GitHub issueSecurity warning while building: “warning Workspaces can only be enabled in private projects”
It is the first time I am seeing this warning while building tinymce.
Tiny Master => ~6.1.0 Windows Yarn 1.22.19
The package.json file of Tiny begins with:
{
"name": "root",
"private": true,
"workspaces": [
"modules/*"
],
...
So what? The required declaration of private: true is done. What is the reason for this security warning?
Issue Analytics
- State:
- Created a year ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Getting "Workspaces can only be enabled in private projects ...
Worktrees used to be required to be private (ie list "private": true in their package.json). This requirement got removed with the 2.0 release ......
Read more >Package 'EntityFramework 6.2.0' was restored using ...
In my case, my project was Core 2.2. I installed (NuGet) Microsoft.EntityFrameworkCore v2.2.4 first and all built fine.
Read more >Releases - Local - Local WP
Download Local 6.1.0 as Linux deb (Ubuntu, Debian, Mint) ... What's New in Local 6.1.0. Improvements ... This add-on only works on macOS...
Read more >CAS 6.1.0 RC1 Feature Release - Apereo Blog
We strongly recommend that you take advantage of the release candidates as they come out. Waiting for a GA release is only going...
Read more >Macbook M1 install genefilter failed
i have solved this problem by myself. share with you. you need to download gfortran in path /opt/R/arm64/bin this website helped me: ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ok - and I solved the grunt-cli warning.
In my build script I had added:
yarn add grunt-cli
But there was no need for this line anymore. => Everthing fine
A simple upgrade of our transitive dependencies upgraded
keyv
and fixed the problem!