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

vite-plugin-integrated

v1.1.10

Published

### En It happens that you need to write a small reactive interface and implement it into some old project, and since with each build js and css bundles are called differently (and this is correct), it is not possible to simply connect everything and thr

Downloads

8

Readme

vite-integrated-plugin

En

It happens that you need to write a small reactive interface and implement it into some old project, and since with each build js and css bundles are called differently (and this is correct), it is not possible to simply connect everything and throw it into the layout <div id="root">

This plugin will help solve this problem. It will allow you to generate in addition index.html another thread file, for example index.tpl (as in php-smarty) and write all the correctly connected scripts and styles into it according to the template described in index.ejs

below is an example of a js template and plug-in connection.

Also, in options, you can throw any data and use it in ejs

Ru

Бывает так что нужно написать небольшой реактивный интерфейс и внедрить его в какой-нибудь старый состоявшийся проэкт а так как при каждом билде js и css бандлы называются по разному (и это правильно) не возможно просто подключить все и закинуть в верстку <div id="root">

Этот плагин поможет решить эту проблему. Он позволит вам сгенерировать помимо index.html еще какой-нить файл например index.tpl (как в php-smarty) и в него записать все правильнпо подключенные скрипты и стили по шаблону описанному в index.ejs

ниже приведен пример ejs шаблона и подключение плагина.

Также в options можно прокинуть любые данные и использовать в ejs

usage

npm i vite-plugin-integrated
or
npm jsr i @traineratwot/vite-plugin-integrated
function viteIntegratedPlugin(
	{
	  templatePath: string,// ejs template
	  name        : string, //name output file
	  options:{}
  }
){}
// vite.config.ts
import { viteIntegratedPlugin } from './plugin/index.js'

export default {
	plugins: [
		viteIntegratedPlugin({
								 templatePath: 'index.ejs',
								 name        : 'index.tpl'
		}
		)
	],
}
<!--index.ejs template for smarty-->
<% scripts.forEach(function(script) { %><script type="module" crossorigin src="<%= script %>"></script><% }) %>
<% styles.forEach(function(style) { %><link rel="stylesheet" href="<%= style %>"><% }) %>
<div id="app"></div>
<!--index.ejs template for easy connection to the browser -->
(function() {
function add(type, value) {
	let element
	if(type === 'script') {
		element = document.createElement('script')
		element.type = 'module'
		element.crossorigin = true
		element.src = value
	}
	if(type === 'style') {
		element = document.createElement('link')
		element.rel = 'stylesheet'
		element.href = value
	}
document.body.appendChild(element)
}
<% scripts.forEach(function(script) { %>add('script','<%=script%>') <% }) %>
<% styles.forEach(function(style) { %>add('style','<%=style%>') <% }) %>
})()