hi! it is not the best example i can imagine but here is a quick demo showing how to use resources inside xlsx recipe, just change the default language between enand es to see the difference.

hi! do you mean the default gridlines that comes with excel?

i think you can only get rid of it if you change background color of multiple cells, to do that you will need to tweak the xml representation of the excel to define the colors, to see how this representation should look like check this reference to the Office Open XML spec

you are welcome, to be honest, npm and its dependencies can be a little bit tricky to understand 😄

for the record, the fix that we were talking about is present in jsreport-core 2.1.1, which it is present in jsreport 2.2.0, so you just need to have jsreport on 2.2.0, no need to install or update anything related to core (it does not matter that core is not on 2.2.0, the important one is jsreport to be in 2.2.0)

hi! i think this is caused by having duplicated jsreport-core in your deps, probably you have both jsreport and jsreport-core in your package.json which is not supported, inside your project you must have installed as direct dependency either jsreport or jsreport-core, not both. one way to see if you have duplicated jsreport-core in your dependencies tree is to run npm ls jsreport-core in your project. if you have duplicated jsreport-core the ouput will look something like this:

jsreport2-test@0.0.1 /Volumes/DATA/workspace/jsreport2-test
├─┬ jsreport@2.2.0
│ └── jsreport-core@2.1.1
└── jsreport-core@2.2.0

it should be just one reference to jsreport-core, for your case you just need to update jsreport to 2.2.0, remove jsreport-core from your package.json. so it will be better for you to reinstall again without having jsreport-core listed in your package.json

yes, you can add those shared helpers as an asset, see here for the docs and see this post to find some explanations and a screenshot. just note that when you mark an asset as a global helper it will be shared to all templates, if you just want to share the helpers to just some of them, then you can put the helpers in an asset (but don't mark it as global helper) and then import the asset in each template helpers section, if you will do that then make sure to import the asset with the right encoding, in this case string encoding

another weird things, why your logs show other two requests correctly completed before failing in the third request? was the report working before? or does the report render some child templates, header or footer when it is being run?

hmm i replicated your same directory structure (project on /var/jsreport) and started jsreport in the same way (using jsreport start) on my machine (OSX) and i can only see that error when i actually don't have the palette module installed. when the palette is installed on my project (/var/jsreport) then i can run the script normally. are you sure you installed palette correctly on /var/jsreport, for example for me the install of palette required to have some other low level packages listed here, after having those low level things in my machine the install of palette was ok. another check will be to run the npm ls palette command on the /var/jsreport-test directory. you should see a result like this:

jsreport-server@ /var/jsreport-test
└── palette@0.1.1

we will see, at first i can't tell you if it is easy to back-port it to 1.x, we usually don't do that, but let's see.. if the change is easy to fix and back-port it would not take so much effort it can be done, but no promise

hi! hmm that should work.. can you share what is the jsreport version you are using? and also can you share all the logs that you get from starting jsreport until you render the report and get the error about not finding google-palette module?