Initialize Nx Monorepo workspace for gridweaver#1
Conversation
Co-authored-by: jchoi2x <2028917+jchoi2x@users.noreply.github.com>
Co-authored-by: jchoi2x <2028917+jchoi2x@users.noreply.github.com>
|
@copilot What happened to the eslint configurations? |
Co-authored-by: jchoi2x <2028917+jchoi2x@users.noreply.github.com>
The ESLint configuration was missing because
Added Vitest via
The React library includes Vitest tests. Fixed in commit 6112c41. |
Co-authored-by: jchoi2x <2028917+jchoi2x@users.noreply.github.com>
Co-authored-by: jchoi2x <2028917+jchoi2x@users.noreply.github.com>
|
@copilot Make sure the packages are publishable, they need to build correctly and have appropriate fields defined in their package.json. Verify that the built files are how they need to be. |
Co-authored-by: jchoi2x <2028917+jchoi2x@users.noreply.github.com>
All libraries are now configured as publishable packages with Vite bundling:
Build output for each library includes:
Fixed in commit d1c2b13. |
Co-authored-by: jchoi2x <2028917+jchoi2x@users.noreply.github.com>
Co-authored-by: jchoi2x <2028917+jchoi2x@users.noreply.github.com>
Co-authored-by: jchoi2x <2028917+jchoi2x@users.noreply.github.com>
Initialize a schema-driven UI library workspace that will store AG Grid definitions in a database and render them dynamically.
Changes
tspreset using npm package manager@nx/react,@nx/node,@nx/eslint, and@nx/vitefor React, Node.js, ESLint, and Vitest support@gridweaver/core(libs/core) - Core library using @nx/node:lib@gridweaver/db-mongodb(libs/db-mongodb) - MongoDB database library using @nx/node:lib@gridweaver/api-hono(libs/api-hono) - Hono API library using @nx/node:lib@gridweaver/react(libs/react) - React UI library using @nx/react:libexports,files,publishConfig, and other fields required for npm publishingzod- schema validationhono- web frameworkmongoose- MongoDB ODMreact,react-dom- UI frameworkag-grid-community,ag-grid-react- grid componentsangular-expressions- expression evaluationVerification
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.