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

svelte-prefix-loader

v1.0.3

Published

Svelte component autoloader

Downloads

4

Readme

svelte-prefix-loader

The plugin svelte-prefix-loader allows you to specify the directory from which you want to autoload the components, depending on the prefixes in the tag name.

Install

npm install --save-dev svelte-prefix-loader

or

npm i -D headmad/svelte-prefix-loader

Usage

// rollup.config.js

import svelte from "rollup-plugin-svelte"
import prefixLoader from "svelte-prefix-loader"
import myHandler from "./plugins/myHandler.js"

// Other imports

const prefixLoaderConfig = {
  App: './[prefix]/[block]/[block][-elem].svelte',
  My: myHandler
}

module.exports = {
  ...
  plugins: [
    svelte({
      preprocess: [ prefixLoader(prefixLoaderConfig) ]
    })
  ]
  ...
}
  • In path template, you can use PascalCase lettering. For example:
<MyHeaderLogo />

./[prefix]/[block][-elem].svelte => ./my/header-logo.svelte
./[Prefix]/[Block][Elem].svelte => ./My/HeaderLogo.svelte
  • In square brackets, you can use any simbols before keyword (prefix, block, elem). For example:
<MyHeaderLogo />

./[prefix]/[block][__elem].svelte => ./my/header__logo.svelte
  • If tag has no Block or Elem section, template just skip they in result. For example:
./bem/[block][/__elem][/block][__elem].svelte

<MyHeader /> => ./bem/header/header.svelte
<MyHeaderLogo /> => ./bem/header/__logo/header__logo.svelte

Also

As a path you can specify a function that should return string - path to svelte-file

The sample code of the handler function:

//myHandler.js
const path = require('path')

module.exports = function(rootDir, {prefix, block, elem}) {
    return path.join(rootDir, `/${prefix}/${block}${elem ? '-' + elem : ''}.svelte`)
}

Parameters

  • rootDir String. Path to dir of root svelte-file (App.svelte)
  • prefix String. First word in tagName. Exemple, in tag <AppPageHeader />, prefix is "App"
  • block String. Second word in tagName. Exemple, in tag <AppPageHeader />, block is "Page"
  • elem String. Third word in tagName. Exemple, in tag <AppPageHeader />, elem is "Header"