hguerrero opened a new pull request, #8759:
URL: https://github.com/apache/camel/pull/8759

   - [x ] Make sure there is a [JIRA 
issue](https://issues.apache.org/jira/browse/CAMEL) filed for the change 
(usually before you start working on it).  Trivial changes like typos do not 
require a JIRA issue.  Your pull request should address just this issue, 
without pulling in other changes.
   - [x ] Each commit in the pull request should have a meaningful subject line 
and body.
   - [x ] If you're unsure, you can format the pull request title like 
`[CAMEL-XXX] Fixes bug in camel-file component`, where you replace `CAMEL-XXX` 
with the appropriate JIRA issue.
   - [x ] Write a pull request description that is detailed enough to 
understand what the pull request does, how, and why.
   - [x ] Run `mvn clean install -Psourcecheck` in your module with source 
check enabled to make sure basic checks pass and there are no checkstyle 
violations. A more thorough check will be performed on your pull request 
automatically.
   Below are the contribution guidelines:
   https://github.com/apache/camel/blob/main/CONTRIBUTING.md
   
   This PR allows using ES modules with the JavaScript DSL by adding the IO 
permission to the GraalVM context. Also, we are using an ES module name for 
processing. This will allow importing `node_modules` from the npm repository 
and use them in the route through process functions.
   
   Example of the new route:
   
   ```js
   // camel-k: language=js
   import { faker } from "./node_modules/@faker-js/faker/dist/esm/index.mjs";
   
   const proc = (e) => {
     e.getIn().setBody(faker.name.fullName());
   };
   
   // Write your routes here, for example:
   from("timer:js?period=30000").routeId("js").process(proc).log("${body}");
   ```


-- 
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: commits-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to