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

karma-razor-preprocessor

v0.0.3

Published

A preprocessor for Karma that strips out Razor syntax from .cshtml files to allow integrated scripts to be tested.

Downloads

6

Readme

karma-razor-preprocessor

A preprocessor for Karma that strips out Razor syntax from .cshtml files to allow integrated scripts to be tested.

Installation

$ npm install karma-razor-preprocessor

Purpose

The purpose of this preprocessor is to allow developers to test JavaScript code that is embedded within Razor files. Although it is highly recommended to separate scripts into their own files (for reusability, caching, and performance reasons) sometimes you have to work with code that is what it is. This preprocessor should help with that, at least a little bit.

Configuration

The razorPreprocessor configuration block accepts only one object, named replacementDictionary. The replacementDictionary object is an array of objects. Each object in the array (that is, each replacement dictionary) must have a fileName property and a lookups property. The fileName property should be the name of the file to match (the file name only, not the fully qualified path) and the lookups property should be an array. Each item in the lookups array (that is, each lookup) must have a searchString property and a replacementString property. These values are used to perform string replacement in the <script> blocks.

razorPreprocessor: Object
 replacementDictionary: Array
  fileName: String    
   lookups: Array    
    searchString: String      
    replacementString: String
// karma.config.js
module.exports = function(config) {
  config.set({
    preprocessors: {
      'Views/**/*.cshtml': ['razor']
    },

    files: [
      '*.js',
      'Views/**/*.cshtml'
    ],

    // if you have defined plugins explicitly, add karma-razor-preprocessor
    // plugins: [
    //     <your plugins>
    //     'karma-razor-preprocessor',
    // ],
    
    razorPreprocessor: {
      // define the replacements that should take place in specific files
      replacementDictionary: [
        {
          fileName: 'File1.cshtml', lookups: [
            { searchString: '@CustomHelper(Model)', replacementString: '{}' }
          ]
        },
        {
          fileName: 'File2.cshtml', lookups: [
            { searchString: '@CreateALink()', replacementString: '{}' }
          ]
        }
      ]
    },
  })
}

How does it work?

This preprocessor strips all <script> blocks out of CSHTML (Razor) files and puts them in a separate file (in memory) for testing. The preprocessor will also run string replacement in the stripped out <script> blocks to get rid of syntax errors when HTML helpers are used in the markup.

For instance this File1.cshtml:

@model Person
<html ng-app="demo">
  <head>*snip*</head>
  <body>
    <div>@ViewBag.TitleValue</div>
    <script>
      angular.module('demo', []).controller('demoController', ['$scope', function($scope) {
        $scope.model = @WriteJson(Model);
        
        $scope.buildName = function() {
          return $scope.model.firstName + ' ' + $scope.model.lastName;
        };
      }]);
    </script>
  </body>
</html>

will be converted to just this:

angular.module('demo', []).controller('demoController', ['$scope', function($scope) {
  $scope.model = {firstName: 'Mickey', lastName: 'Mouse'};
  
  $scope.buildName = function() {
    return $scope.model.firstName + ' ' + $scope.model.lastName;
  };
}]);

when this configuration is used:

razorPreprocessor: {
  // define the replacements that should take place in specific files
  replacementDictionary: [
    {
      fileName: 'File1.cshtml', lookups: [
        { searchString: '@WriteJson(Model)', replacementString: '{firstName: \'Mickey\', lastName: \'Mouse\'}' }
      ]
    }
  ]
},