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

@swissquote/crafty-preset-maven

v1.27.0

Published

<table> <tr><th>Compatible Runners</th><td>

Downloads

23

Readme

Works with any runner

N/A

N/A

[TOC]

Description

This preset allows you to use crafty within a Maven build (with frontend-maven-plugin). This will discover you pom.xml and get the right folder in target for you.

You can use it either with Webjars or Webapps.

Installation

npm install @swissquote/crafty-preset-maven --save
module.exports = {
  presets: ["@swissquote/crafty-preset-maven"],
  mavenType: "webapp" // or "webjar"
};

Usage

The destination directory is calculated using crafty-preset-maven and the mavenType option.

You can set the destination path manually but it's recommended to change the mavenType of your bundle to either webapp or webjar instead.

This is the default for each:

  • webapp: ${project.build.directory}/${project.build.finalName}/resources
  • webjar: ${project.build.outputDirectory}/META-INF/resources/webjars

This preset's role is to replace config.destination which is used to create the destination for each bundleType (destination_js, destination_css ...)

Example

If we take the following configuration:

module.exports = {
    presets: [
        "@swissquote/preset-maven",
        "@swissquote/crafty-preset-babel",
        "@swissquote/crafty-runner-webpack"
    ],
    mavenType: "webjar",
    js: {
        library: {
            source: 'js/index.js',
        }
    }
}

The path of the final file will be :

                                                       ↓ "js" or "css" is added depending on bundle type
<maven_root>/target/classes/META-INF/resources/webjars/js/library.min.js
             ↑ Default path for webjars                   ↑ Inferred from the bundle name

Override destination with an environment variable

If your build is running from within Maven, it's pointless to re-calculate the destination path, you can pass it using the TARGET_BASEDIR environment variable.

This is how to do it in frontend-maven-plugin

<plugin>
   <artifactId>frontend-maven-plugin</artifactId>
   ...
   <configuration>
      ...
      <environmentVariables>
         ...
         <!-- This values is for webapps -->
         <TARGET_BASEDIR>${project.build.directory}/${project.build.finalName}</TARGET_BASEDIR>

         <!-- This value is for webjars -->
         <TARGET_BASEDIR>${project.build.outputDirectory}</TARGET_BASEDIR>
      </environmentVariables>
   </configuration>

   ...
</plugin>

Options

| Option | Type | Optional ? | Description | | ----------- | ------ | ---------- | ---------------------------------------------------------------- | | mavenType | String | No | Must be "webjar" or "webapp" decides where to put the files. |