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

@samokat/parcel-plugin-real-env

v1.0.0

Published

It is a really simple plugin.

Downloads

2

Readme

parcel-plugin-real-env

It is a really simple plugin.

Install it:

yarn add -D @samokat/parcel-plugin-real-env

Modify your html files:

<!-- index.html -->

<!-- ... -->
<script src="#/path-to-any-dir/file-name.env.js"></script>
<!-- ... -->

After building you will get something like this (no more hashes 😎):

<!-- index.html -->

<!-- ... -->
<script src="/path-to-any-dir/file-name.env.js"></script>
<!-- ... -->

That's all.

Why?

Our apps must follow 12 factors, and we inject file with current environment at start application's docker container. This file absent in build-time, the plugin provides way to ignore *.env.js files.

And what?

Common *.env.js look like this:

window._env_ = {
  API_URL: "https://some-service-api.samokat.io",
}

We don't recommend use this global variable directly, because in development-mode, we have no *.env.js files and noone can create this variable. We wrote a simple wrapper for resolve this issue — abstract-env, just try it.

Please, pay attention. Your code must loaded strictly after *.env.js file.

You can use synchronous loading:

<!-- index.html -->

<!-- ... -->
<script src="#/path-to-any-dir/file-name.env.js"></script>
<script src="./app.js"></script>
<!-- ... -->

Or, asynchronous loading:

<!-- index.html -->

<!-- ... -->
<script defer src="#/path-to-any-dir/file-name.env.js"></script>
<script defer src="./app.js"></script>
<!-- ... -->

Be carefully, if you add async attribute, scripts can be executed in other order. Use defer and everything will be OK.

Limitations

This is a really specific library. It transforms only script tags in .html files, which src ends .env.js and starts with hash (#). If you want more flexible solution, try parcel-plugin-html-root-syntax.

Special thanks

Source code of this plugin based on parcel-plugin-html-root-syntax. We just adapted code for our narrow specificity. Thanks, folks!