[core] Cleanup the repository & move over some core files

[mnajdova]

Moved over some proprietary files from the core repository. I set up the workspace and enabled the following commands:

pnpm install
pnpm deduplicate
pnpm build
pnpm run --filter=@app/next-app dev
pnpm run --filter=@app/vite-app dev
pnpm run --filter=@app/next-app build
pnpm run --filter=@app/vite-app build

Next step:

• enable the CI checks
• enable the generateProptypes script
• try and do a dry run on the release scripts
• try to add one Material UI component in the apps (referring the @mui/material@next as external dependency)

[oliviertassinari]

Is this going to keep the git history like @michaldudak did for Base UI?

[mnajdova]

Yes, I did the same here, keeping the history the following directories:

packages/pigment-css-nextjs-plugin
packages/pigment-css-react
packages/pigment-css-unplugin
packages/pigment-css-vite-plugin
packages/pigment-nextjs-plugin
packages/pigment-vite-plugin
packages/pigment-unplugin
packages/pigment-react
packages/zero-next-plugin
packages/zero-runtime
packages/zero-tag-processor
packages/zero-vite-plugin
apps/

The history available: https://github.com/mui/pigment-css/commits/master/

This PR starts with setting up everything, workspace, scripts, etc, similar to mui/base-ui#1

[mnajdova]

GitHub is strange, I can't see my last commits 😕

[brijeshb42]

It's showing Processing Updates at the top. So it might take a while before showing the commits.

[michaldudak]

I couldn't find any major issues. It's definitely worth setting up the CI as soon as possible to run checks on PRs.

[mnajdova]

I am closing the PR, I pushed the branch directly, GH seems to be very slow/buggy. Here is the commit: 18da3fc I will proceed with the CI checks.

[mnajdova]

I am closing the PR, I pushed the branch directly, GH seems to be very slow/buggy. Here is the commit: 18da3fc I will proceed with the CI checks.

Alright, the issue is that I created the fork when the repository was private, and I didn't change my own fork to public. I am creating another fork as public, this should resolve future issues.