Posts made by rchancey

Humm.. sorry not sure I am following.. that setting is not on in the invoice example.. and it sill loads the fonts
https://playground.jsreport.net/w/rchancey/QN0Hsolm

I set that setting and still no fonts in the vanilla project I made. .. just the normal css not even the js.
Something else preventing it from loading the css external in the bare bones project?

I am not really following.. how do I know when to set the window.JSREPORT_READY_TO_START=true? I have no idea when the js has loaded for the styles from the kit.. sorry if I missed something?

Yes and no.
I was able to add the fonts to the invoice fork:
https://playground.jsreport.net/w/rchancey/uq1rZNy4

but when I created my own initial report not even the CDN works.. can see that here:
https://playground.jsreport.net/w/rchancey/QN0Hsolm

that's very odd because it works fine in your invoice example.. must be some config missing from the blank start?

You can see in the screen shot the fonts show fine with the normal CDN:

but if I use the kit.. nothing:

Also if you paste the script URL into your browser the js css will show up.. its fully open and accessible. So somehow js report must not like the JS file?

I am trying to use a purchased set of font awesome.. the normal CDN link works fine and when I use a <script> tag for the kit it works fine.. but passing that to jsreprot does not render the fonts. Just get squares.

Here is the kit stuff from fontawesome.. its supported by CDN
https://fontawesome.com/docs/web/setup/use-kit

Is there a way to use this with JS report?

This does work with normal HTML but again when I pass that HTML to jsreprot.. it does not render the fonts.

here is my kit: <script src="https://kit.fontawesome.com/3a57f86f87.js" crossorigin="anonymous"></script>

Any insight would be appreciated.

https://github.com/npm/write-file-atomic
I found that.. which seems to do the same thing . it downloads and renames (depends on the rename being atomic on the os, Windows it is not).

so your solution is a good one.. I will move to use this package and change my fs.writeFileSync to use this package (which seems to do your solution under the covers) and will handle this .. good call.

btw.. I spoke to one of my peers.. and he likes your solution to avoid multiple calls all writing the same file. I wonder if there is an atomic writeFileSync that will fail if the file exists already?

well I use writeFileSync, as well as chmodSync.. so it 'should' wait until written. I have not seen any issues so far in my testing. I have not performance tested.

So in theory if we run without any of those functions being 'done' the report will error.
So in theory this is all very tight. I say in theory because only way to really know is to do a performance test.

I am not sure the suggestion is gonna work because then you are talking about the time between renames and how do you wait on that? (because I think rename can also fail if the chrome is being used.

Downloading each time is the most robust approach, but until I see where the getObject, writeFileSync and chmodSync re not really sync.. I am ok not to add the additional complexity of renaming.

My entire jsreport is sync..so I need it to all hold until the report is final.

I am more than happy to report back here if I see the function I created is not working well for larger number of requests .. for sure..

thoughts?

Below is my function.

const getBucket = promisify(s3.getObject).bind(s3)
...
 getBucket(config).then((response) => {
        fs.writeFileSync('/tmp/headless-chromium', response.Body);
        fs.chmodSync('/tmp/headless-chromium', '755');
...
}

@jan_blaha that article was outstanding. Thank you for doing that and putting it together. Very clean solution.
I did change it all sync calls and I also don't download chrome if it already exists .. I added that bit just fyi.

Thank you again for documenting that.

ahh.. I did not. We already have js reports running as lambda for a long time.. I was trying to not mess with it and just insert the chrome. Let me look through and try that and see how it works. Thanks for putting that together!

oh.. I am doing a very simple foo bar example . template below: Any suggestions would be really appreciated.

        content: "<h1>Hello  {{foo}} </h1>",
        recipe: 'chrome-pdf',
        engine: 'handlebars',
        mimeType: "application/pdf",
        filename: "report.pdf"
    }

I am not getting a return from the render function.. my question is can I enable more logging somehow to see where jsreport is getting hung up? details below:

I am using chrome-aws-lambda to enable running chrome on lambda. I am able to run the example code from this package and it works. Takes about 3 seconds to run.

sample code here:

 (async () => {
      log.info(`loading chrome `);
      const chromium = require('chrome-aws-lambda');

      let executablePath =  await chromium.executablePath;
      log.info(`executable path ... `, executablePath);

      let browser = await chromium.puppeteer.launch({
        args: chromium.args,
        defaultViewport: chromium.defaultViewport,
        executablePath: await chromium.executablePath,
        headless: chromium.headless,
      });
    log.info(`executable path ... `, chromium.executablePath);
      log.info(`new page ... `);
      let page = await browser.newPage();
      log.info(`new page ... `, page);
      await page.goto(event.url || 'https://example.com');

      let result = await page.title();
      log.info(`result `, result);
    })();

I get back:

"log": [
        "result ",
        "Example Domain"
    ],

The path for the chromium is /tmp/chromium..

 "log": [
        "executable path ... ",
        "/tmp/chromium"
    ],

I pass this to jsreport:

const jsreport = require('jsreport-core')({
    tasks: {
        allowedModules: '*',
        strategy: 'in-process'
    },
    loadConfig: false,
    studio: { enabled: false },
    allowLocalFilesAccess: true,
    dataDirectory: path.join(os.tmpdir(), 'jsreport'),
    templatingEngines: { allowedModules: '*' },
    extensions: {
        "chrome-pdf": {
            "launchOptions": {
                executablePath: "/tmp/chromium",
                "args": ["--no-sandbox"]
            }
        }
    }
});

and I guess it loads since it did not error.. but it never returns from render.

oh.. these are my dependancies. I also pass the flag for pupppeter not to download chrome since it is too large for lambda.. hence using the package

"dependencies": {
    "chrome-aws-lambda": "^1.17.1",
    "config": "1.21.0",
    "handlebars": "^4.1.0",
    "handlebars-helpers": "0.10.0",
    "handlebars-intl": "1.1.2",
    "jsonwebtoken": "8.2.1",
    "jsreport-chrome-pdf": "^1.4.0",
    "jsreport-core": "^2.4.3",
    "jsreport-handlebars": "^2.0.1",
    "jsreport-html-to-xlsx": "^2.3.0",
    "jsreport-xlsx": "^2.0.10",
    "mongoose": "4.13.17",
    "puppeteer": "1.12.2",
    "regenerator-runtime": "^0.13.2",
    "upgrade": "1.1.0",
    "uuid": "3.1.0"
  },

any thoughts on where jsreport might be getting stuck?

Well, you solve it ! :) .. interestingly enough I just used the triple bracket and it worked PERFECT. I did not even have to use the div.. very nice.. I did not know the {{{ even existed.. very nice.. thank you !

I have a string that has embedded html and I am trying to render it. I normally use something like: <div dangerouslySetInnerHTML={{ __html: string }}/>

I can't get this to work in jsreport since the double bracket tells JS Report that the __html is a function.

Is is there a way to have js report render the string a html???

I need something like <div dangerouslySetInnerHTML={{ __html: {{myString}} }}/>.. which just blows up

ok.. @bjrmatos Thanks for all your help so far.

I am trying to move to the latest 2.2.0.. and while it works local (meaning no error finding the abs helper) it seems to not find the helper when we deploy to bitbucket. And since I can't run it local I can't exactly test it..

so wonder if you can tel me what would need to change to enable 2.2.0?

here is my report loading

const jsreport = require('jsreport')({
    tasks: {
        allowedModules: '*',
        strategy: 'in-process'
    },
    loadConfig: false,
    logger: {
        file: { enabled: false},
        silent: true
    },
    studio: { enabled: false },
    allowLocalFilesAccess: true,
    dataDirectory: path.join(os.tmpdir(), 'jsreport'),
    templatingEngines: {   allowedModules: '*'},
});

and here is my package

"dependencies": {
    "config": "^1.21.0",
    "debug": "^3.0.1",
    "handlebars": "4.0.11",
    "handlebars-helpers": "0.10.0",
    "handlebars-intl": "1.1.2",
    "jsonwebtoken": "8.2.1",
    "jsreport": "2.2.0",
    "mongoose": "^4.13.17",
    "npm": "^6.4.1",
    "upgrade": "1.1.0",
    "uuid": "^3.1.0"
  },

Off the top of your head do you know what I need to do to enable 2.2.0? You had mentioned I did 'not' need to do certain things when using 1.10.. but I assume I need to do something to get 2.2.0 to work?

any suggestions.

again all I did was move to 2.2.0 and on bitbucket it says can't find the 'abs'. helper. same issue we had earlier.

Thank you .. that worked great! ..

now the question is am I brave enough to move to V2!!?!??! :)

ok.. will try. I did try to go to V2 of js report. but it got that same error 'missing abs helper'. I was going to debug that later.. but jsreport 1 is working fine..

thank you...let me try!

Trying to move enable html-to-xlsx recipe and running into an error:

reporting:reporting.js:90  JSReport render error TypeError: Cannot set property 'contentType' of undefined
    at module.exports (/opt/atlassian/pipelines/agent/build/node_modules/jsreport-html-to-xlsx/lib/responseXlsx.js:35:29)
    at Object.execute (/opt/atlassian/pipelines/agent/build/node_modules/jsreport-html-to-xlsx/lib/htmlToXlsx.js:71:14)
    at <anonymous>
 reporting:index.js:44  report error: TypeError: Cannot set property 'contentType' of undefined
    at module.exports (/opt/atlassian/pipelines/agent/build/node_modules/jsreport-html-to-xlsx/lib/responseXlsx.js:35:29)
    at Object.execute (/opt/atlassian/pipelines/agent/build/node_modules/jsreport-html-to-xlsx/lib/htmlToXlsx.js:71:14)
    at <anonymous>

It is happening from this code (see screen cap).. line 35.

I have no idea why meta would be null.. nor even where it gets populated.
I am doing the sample code from earlier, and just changed to html-to-xlsx and added a table to the content.. simple as that.

I did add the "jsreport-html-to-xlsx": "2.1.2", to the package..

my package.json

"dependencies": {
    "config": "^1.21.0",
    "debug": "^3.0.1",
    "handlebars": "4.0.6",
    "handlebars-helpers": "0.10.0",
    "handlebars-intl": "1.1.2",
    "jsonwebtoken": "8.2.1",
    "jsreport": "1.10.0",
    "jsreport-html-to-xlsx": "2.1.2",
    "mongoose": "^4.13.17",
    "npm": "^6.4.1",
    "upgrade": "1.1.0",
    "uuid": "^3.1.0"
  },

and my content

 let template = { content: `<table> <tr> <td style="height: 50px; font-size: 35px">Hello world</td> <td>world</td> </tr> <tr> <td style="width: 20px; text-align:right">right</td> <td>world</td> </tr> <tr> <td>world</td> <td>world</td> </tr> </table>`,
        engine: 'handlebars',
        helpers: `
        const handlebars = require('handlebars');

        const helpers = require('handlebars-helpers')({
          handlebars: handlebars
        });
      `,
      phantom: {
        orientation: "portrait",
       format: "A4",
     },
        recipe: 'html-to-xlsx' };
        let data = {
            "foo": "world"
        };

I did try to specify a 'phantom' config.. but same error..

any ideas? @bjrmatos ?

This worked!! .. at least locally :) I then pushed to bitbucket and got the 'abs helper not found' but that is probably something on our end. So your suggestion worked.

Thanks @bjrmatos

ok @bjrmatos .. I include the same code but just moved to the latest js report.. 2.2.0.. and I now get that same error can't find abs..
I put the entire project here like last time..
https://drive.google.com/open?id=1qtx0PKH65TTZt8yP59OlP10jdtvTubQ-

Moving to the 2.2.0 now has 2 versions of handlers!.. dang..

I tried the dedupe and it does not.. just has same..

Can you do some magic here and show me what I can do?

again this is the sample.. so if get this to work others can also copy it.

Thank you for helping @bjrmatos .. really appreciate your time

THAT WORKED!!! WOOT!!
super secret studio-enabled.false flag.. yah! :)

Thank you @bjrmatos !.

ok. .so the last thing is to move this to the latest 2.2.0..

and just for others who might come behind us with this issue on lambda.. here is the final config:

const jsreport = require('jsreport')({
    tasks: {
        allowedModules: '*',
        strategy: 'in-process'
    },
    loadConfig: false,
    logger: {
        file: { enabled: false},
        silent: true
    },
    studio: { enabled: false },
    allowLocalFilesAccess: true,
    dataDirectory: path.join(os.tmpdir(), 'jsreport'),
    templatingEngines: {   allowedModules: '*'},
  
});

and the final package.json

"dependencies": {
    "config": "^1.21.0",
    "debug": "^3.0.1",
    "handlebars": "4.0.6",
    "handlebars-helpers": "0.10.0",
    "handlebars-intl": "1.1.2",
    "jsonwebtoken": "8.2.1",
    "jsreport": "1.10.0",
    "mongoose": "^4.13.17",
    "npm": "^6.4.1",
    "upgrade": "1.1.0",
    "uuid": "^3.1.0"
  },

yah.. I added enabled: false and got past that error.. but now I am getting this error:.. why is this trying to load the jsreport-studio?

any idea where that is coming from and how to turn that off ?? :)

the log is below.. here is my code:

import config from 'config';
import AWS from 'aws-sdk';
import uuid from 'uuid/v4';
import {
    Logger
} from './common';

const log = new Logger();

const path = require('path');
const os = require('os');

const jsreport = require('jsreport')({
    tasks: {
        allowedModules: '*',
    },
    loadConfig: false,
    logger: {
        file: { enabled: false},
        silent: true
    },
    dataDirectory: path.join(os.tmpdir(), 'jsreport'),
    templatingEngines: {   allowedModules: '*'},
    // connectionString: { 'name': 'fs', syncModifications: true }
});
// jsreport.use(require('jsreport-fs-store')());
// jsreport.use(require('jsreport-handlebars')());
// jsreport.use(require('jsreport-phantom-pdf')());

and the package.json

  "dependencies": {
    "config": "^1.21.0",
    "debug": "^3.0.1",
    "handlebars": "4.0.6",
    "handlebars-helpers": "0.10.0",
    "handlebars-intl": "1.1.2",
    "jsonwebtoken": "8.2.1",
    "jsreport": "1.10.0",
    "mongoose": "^4.13.17",
    "npm": "^6.4.1",
    "upgrade": "1.1.0",
    "uuid": "^3.1.0"
  },

"log": [
        "report error:",
        "Error: EROFS: read-only file system, open '/var/task/node_modules/jsreport-studio/static/dist/1.client.js'\n    at Object.fs.openSync (fs.js:646:18)\n    at Object.fs.writeFileSync (fs.js:1299:33)\n    at Reporter.<anonymous> (/var/task/node_modules/jsreport-studio/lib/studio.js:91:10)\n    at emitOne (events.js:121:20)\n    at Reporter.emit (events.js:211:7)\n    at configureExpressApp (/var/task/node_modules/jsreport-express/lib/reporter.express.js:131:12)\n    at module.exports.<anonymous> (/var/task/node_modules/jsreport-express/lib/reporter.express.js:182:5)\n    at /var/task/node_modules/listener-collection/lib/listenerCollection.js:171:33\n    at /var/task/node_modules/listener-collection/lib/listenerCollection.js:151:16\n    at tryCatcher (/var/task/node_modules/bluebird/js/release/util.js:16:23)\n    at Promise._settlePromiseFromHandler (/var/task/node_modules/bluebird/js/release/promise.js:512:31)\n    at Promise._settlePromise (/var/task/node_modules/bluebird/js/release/promise.js:569:18)\n    at Promise._settlePromise0 (/var/task/node_modules/bluebird/js/release/promise.js:614:10)\n    at Promise._settlePromises (/var/task/node_modules/bluebird/js/release/promise.js:693:18)\n    at Async._drainQueue (/var/task/node_modules/bluebird/js/release/async.js:133:16)\n    at Async._drainQueues (/var/task/node_modules/bluebird/js/release/async.js:143:10)\n    at Immediate.Async.drainQueues (/var/task/node_modules/bluebird/js/release/async.js:17:14)\n    at runCallback (timers.js:794:20)\n    at tryOnImmediate (timers.js:752:5)\n    at processImmediate [as _immediateCallback] (timers.js:729:5)"
    ],

any idea what could be making it load the report studio? I have never seen this error before