borinquenkid commented on code in PR #15530:
URL: https://github.com/apache/grails-core/pull/15530#discussion_r3011998820
##########
gradle/rat-root-config.gradle:
##########
@@ -76,6 +83,15 @@ tasks.named('rat') {
'build-logic/.idea/**', // grails-gradle idea directories
'build/**', // build directories
'buildSrc/build/**', // build directories
+ '**/build/**', // all build directories
+ 'node_modules/**', // node modules
Review Comment:
✦ Based on my investigation of the grails-core codebase, Node.js is not a
primary part of the framework's build or runtime system. Its usage can be
categorized into two areas:
1. WebJars (Indirect Usage): The project uses WebJars (e.g.,
org.webjars.npm:bootstrap, org.webjars.npm:jquery) to manage frontend
dependencies. These are npm packages packaged as JAR files, allowing
the project to include them in functional tests and example
applications without requiring a local Node.js installation.
2. Local Development Tools: There is a node_modules directory in the
project root containing tools like repomix, @modelcontextprotocol/sdk, and
hono. These appear to be user-specific tools for AI
interaction (packing the repo for LLMs) or for developing Model
Context Protocol (MCP) servers, rather than core components of Grails.
The absence of a package.json file in the root or sub-modules (other than
those inside node_modules itself) and the lack of Node-related Gradle plugins
confirm that Node.js is not used for the
framework's build process.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
