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

admin-iframe-compatibility

v1.0.106

Published

Compatiblity js to adapt catalog admin to iframe

Downloads

241

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

eduardoformigaeduardoformigamayzabelmayzabelnatamelonatameloaugusto.lazaroaugusto.lazarorafarubimrafarubimjeymissonjeymissonvictorhmpvictorhmplurianlurianarturpimentelarturpimentelanitavincentanitavincentbrunojdobrunojdovtexlab-uservtexlab-useremersonlaurentinoemersonlaurentinoemersonvtexemersonvtexviniagostiniviniagostinilucasaarcoverdelucasaarcoverdelariciamotalariciamotafabitsfabitsgeraldo.fernandesgeraldo.fernandesmateuspontesmateuspontesvitorlgomesvitorlgomespolicarpopolicarpomarcelovicentegcmarcelovicentegcmaianabtmaianabthiagolcmhiagolcmwilliam.silvawilliam.silvawenderwendervcnovaesvcnovaescarolinerpessoacarolinerpessoagianvittoriogianvittoriofilafbfilafbmendescamaramendescamarakevinvtexkevinvtexmyllena.alvesmyllena.alvesenzomercaenzomercajardelymarisjardelymarisrodzacrodzacdaniyelnnrdaniyelnnrdenissilvavtexdenissilvavtexvinhagsvinhagsgeorgebrindeirogeorgebrindeiromarcos_vtexmarcos_vtexluiznickel-vtexluiznickel-vtexrodrigo.albuquerquerodrigo.albuquerqueluisgomes01_extvtexluisgomes01_extvtexsophreisvtexsophreisvtexguigsguigsphilcvlcntphilcvlcntandersonsmedandersonsmed

Keywords

Readme

Internal Docs

There is nothing glamorous to see here

This package is just a static JS with jquery code that runs on catalog admin pages. It is responsible for handling translations for legacy applications, messaging the admin shell to adapt its iframe container height to match its children height, and initializing Crowdin in Context script for legacy apps.

Developing locally

  • Setup:
npm install

  • You will need the requestly chrome extension linked here

  • Open requestly, and create Redirect Rules with the following semantics:

Request URL Contains /npm/admin-iframe-compatibility/index.js
Destination http://localhost:4200/index.js

Request URL Contains /npm/admin-iframe-compatibility/cms-iframe.js
Destination http://localhost:4200/cms-iframe.js
  • Save the rules and leave it on
  • Run the server
    npm start
  • Edit the JS, save it, run npm start again and refresh the admin page to see your changes.

Publishing a new version

Just run:

npm run deploy

or

npm run deploy:beta

A github workflow will be automatically triggered once new tags are pushed to the repository.