npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@jsreport/jsreport-fs-store

v4.0.4

Published

File system based templates store

Downloads

8,337

Readme

@jsreport/jsreport-fs-store

NPM Version

jsreport template store extension. Supports editing templates in the external editors and browser's live reload and preview!

See the docs https://jsreport.net/learn/fs-store

Installation

npm install jsreport-fs-store

Then alter jsreport configuration

{
	'store': { 'provider': 'fs' }
}

Changelog

4.0.4

  • update socket.io, socket.io-client deps to fix audit

4.0.3

  • fix bug with transactions that takes long and locks

4.0.2

  • update rimraf to fix audit

4.0.1

  • fix parameter mutations passed to store methods producing unexpected changes in store
  • add indexes to fs store to improve big import performance
  • fix too many open files open error on windows with big import

4.0.0

  • minimum node.js version is now 18.15.0
  • update studio build against new webpack and babel

3.2.5

  • update deps to fix npm audit warnings

3.2.4

  • update deps to fix npm audit warnings

3.2.3

  • fix $in queries

3.2.2

  • corrupted journal should be cleaned to avoid interval errors

3.2.1

  • fix external entities changes sync reload
  • changes to enable new trustUserCode option

3.2.0

  • properly support absolute path in blobStorage.dataDirectory
  • various optimizations regarding profiler persistence

3.1.0

  • add fs-store ignore option to ignore directories/files during the load
  • add socket.io as explicit dep
  • optimization: don't delete nested folders when updating folder
  • fix losing entities in fs store data directory when updating folder in transaction

3.0.0-beta.1

Adaptations for the v3 APIs

Development

(This section is intended to jsreport extension developers audience.)

Entity definitions

Use splitIntoDirectories attribute in registerEntitySet to use the directory structure for storing. Otherwise the storage will put every entity row into the one single file.

this.documentStore.registerEntitySet("templates", {entityType: "jsreport.TemplateType", splitIntoDirectories: true});

Not every jsreport entity should be spitted into the tree structure. It is especially not desired for the entities where you expect thousands of entries. In this case just remove the splitIntoDirectories attribute.

The second required step is to extend the entity type with name attribute which defines the attribute used for the row directory name. And also adding the document for the attributes you want to extract into dedicated files.

var templateAttributes = {
	...
    shortid: { type: "Edm.String" },
    name: { type: "Edm.String" },
    content: {
        type: "Edm.String",
	    document: { extension: "html", engine: true }
	}
    ...
};

Engines

Engines like handlebars or jade are able to override the default file extension for the template content files. This can be done using file extension resolver....

reporter.documentStore.addFileExtensionResolver(function(doc, entitySetName, entityType, propertyType) {
        if (doc.engine === "handlebars" && propertyType.document.engine) {
            return "handlebars";
        };
    });