klazuka

elm-hot

Error

Ignore

Warn

License

Maintenance

Miscellaneous

Quality

Supply chain risk

Vulnerability

Admins only

Organization members

Dashboard

<upgradeLink>Upgrade</upgradeLink> to access this feature

About

Blog

Socket CLI

Customers

Socket Dependency Search

Docs

Socket for GitHub

Love

Impersonation Mode Active

Update your browser to the latest version for the best experience.

Your web browser is outdated

Use another browser for the best experience.

Your web browser is unsupported

{{count, number}} commits last two months

{{count, number}} critical severity alert

{{count, number}} critical severity alerts

{{count, number}} dependency vulnerability

{{count, number}} dependency vulnerabilities

{{count, number}} development dependencies

{{count, number}} transitive dependencies

{{count, number}} version published last month

{{count, number}} versions published last month

{{count, number}} version published in last two months

{{count, number}} versions published in last two months

{{count, number}} version published last week

{{count, number}} versions published last week

{{count, number}} version published last year

{{count, number}} versions published last year

Socket undergoes annual SOC2 Type II audits. Socket customers can request a copy of the full SOC2 Type II report.

Allows organization owners and admins to access detailed records of actions taken by members of their organization, complete with timestamps.

Prevent compromised packages from infiltrating your supply chain by monitoring for changes in real-time.

Join our Discord community to get help from Socket engineers and other Socket users.

Compare millions of open source packages on socket.dev

Detect malicious code and risky behavior (e.g. network) in your dependencies using "deep package inspection"

All data is encrypted in transit and at rest using industry standard encryption algorithms.

Get a dedicated Socket account manager and access to Socket’s Customer Success team.

Get dedicated support from Socket engineers via email and Slack.

"Shift left" with the Socket Chrome extension and give intervene early, before developers choose risky or low quality dependencies.

Catch developers using risky dependencies and give them a "speed bump" to encourage good behavior

Install the Socket GitHub app to receive real-time dependency scanning and reports with every pull request.

Integrate Socket into your GitHub SCM to prevent risky dependencies from being installed.

Socket scans for vulnerabilities in your dependencies, including CVEs, security advisories, and more.

Socket supports dependencies in many languages, with most popular ecosystems coming in 2024. We've got you covered no matter what languages you use.

Enforce license policies across your organization

Receive a Microsoft Teams message to the channel of your choice anytime Socket runs a new analysis, has a new finding, or a policy has changed.

Get help migrating from Socket's free plan to Socket's paid plans.

Run Socket on-premises or in your own cloud environment.

Query for any dependency (at any version) across your entire organization

Integrate Socket into your CI/CD pipeline to prevent risky dependencies from being deployed to production.

Analyze an entire project to find supply chain risks

Tag projects to organize and filter your projects

Restrict access based on the roles of individual users within an organization.

Receive a Slack message to the channel of your choice anytime Socket runs a new analysis, has a new finding, or a policy has changed.

Socket is SOC2 Type II compliant and undergoes annual audits.

The Socket CLI allows teams to prevent risky dependencies from being installed, and to get dependency insights from the command line.

Socket supports SAML SSO for single sign-on and identity management.

Integrate Socket into your VS Code IDE to prevent risky dependencies from being installed.

Get a POST request anytime Socket runs a new analysis, has a new finding, or a policy has changed.

Socket will analyzed your SBOMs up to a maximum number of dependencies.

API that allows you to analyze a project, lookup package scores and alerts, and more.

Create API tokens to authenticate with the Socket API and CLI.

The number of developers in your team. A developer is someone who made a commit to your organization's repositories scanned by Socket in the past month.

Use Socket to protect your private repositories.

Socket is always free for open source projects.

Socket retains all reporting data for 3 months, 1 year, or a custom term of your choice.

Access the threat feed that powers Socket.

Unlimited scale, self-hosting, and priority support for large teams.

For open-source projects, individuals, and small teams.

For growing teams with enhanced scale, security, and support.

There is a package with a similar name that is downloaded much more often.

There are packages with similar names that are downloaded much more often.

This may not be the package you want!

Instance

Alert Locations

Package

The {{ecosystem}} package {{- packageName}} receives a total of <strong>{{numWeeklyDownloadCount, number}}</strong> weekly downloads. As such, {{- packageName}} popularity was classified as <strong>{{popularity}}</strong>.

Is {{- packageName}} popular?

Is {{- packageName}} safe to use?

Is {{- packageName}} well maintained?

What is {{- packageName}}?

{{packageDescription}}Version: {{versionString}} was published by {{publisherName}}. Start using Socket to analyze {{- packageName}} and its {{dependencyCount, number}} dependencies to secure your app from supply chain attacks.

Sorry, it seems this package was removed from the registry

Package was removed

This package version has been unpublished, mostly likely due to security reasons

Package version was removed

Provide a detailed description of the malware...

Socket fights vulnerabilities and provides visibility, defense-in-depth, and proactive supply chain protection for JavaScript, Python, and Go dependencies.

Socket - Secure your dependencies. Ship with confidence.

Compare versions

{{- packageName}} - npm Package Compare versions

  "description": "Hot code swapping for Elm",

    "url": "https://github.com/klazuka/elm-hot"

[![CircleCI](https://circleci.com/gh/klazuka/elm-hot.svg?style=svg)](https://circleci.com/gh/klazuka/elm-hot)

This package provides the core infrastructure needed for doing hot code swapping in Elm. It supports Elm 0.19 only.

**This low-level package is only intended for authors of Elm application servers.**

If you're looking for something that's easier to use, and you're willing to use Webpack, see [elm-hot-webpack-loader](https://github.com/klazuka/elm-hot-webpack-loader), which is built using this package.

The goal of this package is to provide a reusable core that can be used to provide hot code swapping support in a variety of environments--not just Webpack.

- improved Browser.application support (Browser.Navigation.Key can be stored anywhere in your model now) 

- separated the Webpack loader out into its own package

---------------------------------------------

Injects the hot code swapping functionality into a compiled Elm app.

- takes the Javascript code emitted by the Elm compiler as an input string

- returns a string containing the injected code ready to be `eval`-ed in the browser.   

### Example of how the core API could be used 

const {compileToStringSync} = require('node-elm-compiler');

const injectedCode = elmHot.inject(compileToStringSync(["src/Main.elm"], {}));

In order to provide something similar to `webpack-dev-server` with hot module reloading, an application server could be developed to do the following:

- serve a modified version of the app developer's `index.html` to receive push events from the server

- whenever a source file changes, push an event to the client notifying it that it should fetch new code from the server

    - fetch the new code (the server will re-compile the Elm code and use `elm-hot` to inject the hot-code-swapping logic)

    - the client deletes the old `Elm` object and calls `eval()` on the new code from the server

I have implemented something similar to this for the integration tests. See [test/server.js]() and [test/client.js]() for inspiration.

The above description is probably a bit too vague, so if you would like more details, create an issue.

-------------------------------------------

Elm hot code swapping is based on the work of Flux Xu's [elm-hot-loader](https://github.com/fluxxu/elm-hot-loader).

//////////////////// HMR BEGIN ////////////////////

  MIT License http://www.opensource.org/licenses/mit-license.php

    A note about the environment that this code runs in...

        - `module` (from Node.js module system and webpack)

    assumed in scope after injection into the Elm IIFE:

        - `scope` (has an 'Elm' property which contains the public Elm API)

        - various functions defined by Elm which we have to hook such as `_Platform_initialize` and `_Scheduler_binding`

        //polyfill for IE: https://github.com/fluxxu/elm-hot-loader/issues/16

        if (typeof Object.assign != 'function') {

            Object.assign = function (target) {

                    throw new TypeError('Cannot convert undefined or null to object');

                for (var index = 1; index < arguments.length; index++) {

                    var source = arguments[index];

                    if (source != null) {

                        for (var key in source) {

                            if (Object.prototype.hasOwnProperty.call(source, key)) {

                                target[key] = source[key];

            ? module.hot.data.instances || {}

        if (Object.keys(instances).length === 0) {

            console.log("[elm-hot] Enabled");

        // These 2 variables act as dynamically-scoped variables which are set only when the

        // Elm module's hooked init function is called.

        module.hot.dispose(function (data) {

            // Cleanup pending async tasks

            // First, make sure that no new tasks can be started until we finish replacing the code

            _Scheduler_binding = function () {

                return _Scheduler_fail(new Error('[elm-hot] Inactive Elm instance.'))

            // Second, kill pending tasks belonging to the old instance

                console.log('[elm-hot] Killing ' + cancellers.length + ' running processes...');

                    cancellers.forEach(function (cancel) {

                    console.warn('[elm-hot] Kill process error: ' + e.message);

        function findPublicModules(parent, path) {

                var currentPath = path ? path + '.' + key : key;

                        path: currentPath,

            // Returns true if the Elm app will take over the entire DOM body.

            return typeof elm$browser$Browser$application !== 'undefined'

                || typeof elm$browser$Browser$document !== 'undefined';

            // When embedding an Elm app into a specific DOM node, Elm will replace the provided

            // DOM node with the Elm app's content. When the Elm app is compiled normally, the

            // original DOM node is reused (its attributes and content changes, but the object

            // in memory remains the same). But when compiled using `--debug`, Elm will completely

            // destroy the original DOM node and instead replace it with 2 brand new nodes: one

            // for your Elm app's content and the other for the Elm debugger UI. In this case,

            // if you held a reference to the DOM node provided for embedding, it would be orphaned

            // after Elm module initialization.

            // So in order to make both cases consistent and isolate us from changes in how Elm

            // does this, we will insert a dummy node to wrap the node for embedding and hold

            // a reference to the dummy node.

            // We will also put a tag on the dummy node so that the Elm developer knows who went

            // behind their back and rudely put stuff in their DOM.

            var dummyNode = document.createElement("div");

            dummyNode.setAttribute("data-elm-hot", "true");

            var parentNode = node.parentNode;

            parentNode.replaceChild(dummyNode, node);

        function wrapPublicModule(path, module) {

            var originalInit = module.init;

                module.init = function (args) {

                    var portSubscribes = {};

                    if (typeof args !== 'undefined') {

                        domNode = args['node'] ? wrapDomNode(args['node']) : document.body;

                        domNode = args['node'] && !isFullscreenApp()

                            ? wrapDomNode(args['node'])

                            : document.body;

                        flags = args['flags'];

                        // rare case: Elm allows init to be called without any arguments at all

                        domNode = document.body;

                        flags = undefined

                    initializingInstance = registerInstance(domNode, flags, path, portSubscribes, portSends);

                    elm = originalInit(args);

                    wrapPorts(elm, portSubscribes, portSends);

                    initializingInstance = null;

		{
		"name": "elm-hot",
		"version": "1.0.0",
		"version": "1.0.1",
		"description": "Hot code swapping for Elm",
		@@ -5,0 +5,0 @@ "keywords": [

		@@ -16,2 +16,5 @@ [![CircleCI](https://circleci.com/gh/klazuka/elm-hot.svg?style=svg)](https://circleci.com/gh/klazuka/elm-hot)

		### 1.0.1
		- bug fixes

		### 1.0.0
		@@ -18,0 +21,0 @@ - improved Browser.application support (Browser.Navigation.Key can be stored anywhere in your model now)

		@@ -127,2 +127,8 @@ //////////////////// HMR BEGIN ////////////////////

		function isFullscreenApp() {
		// Returns true if the Elm app will take over the entire DOM body.
		return typeof elm$browser$Browser$application !== 'undefined'
		\|\| typeof elm$browser$Browser$document !== 'undefined';
		}

		function wrapDomNode(node) {
		@@ -163,3 +169,5 @@ // When embedding an Elm app into a specific DOM node, Elm will replace the provided
		// normal case
		domNode = args['node'] ? wrapDomNode(args['node']) : document.body;
		domNode = args['node'] && !isFullscreenApp()
		? wrapDomNode(args['node'])
		: document.body;
		flags = args['flags'];
		@@ -323,2 +331,6 @@ } else {

		if (typeof item.value !== "object") {
		continue;
		}

		for (var propName in item.value) {
		@@ -325,0 +337,0 @@ if (!item.value.hasOwnProperty(propName)) continue;

		@@ -177,2 +177,13 @@ import test from 'ava';

		test('if Browser.Navigation.Key cannot be found, degrade gracefully', async t => {
		const testName = "BrowserApplicationMissingNavKeyError";
		// There was a bug (https://github.com/klazuka/elm-hot/issues/15) which caused an infinite loop
		// when the root of the model was a union type and the Browser.Navigation.Key could not be found.
		const page = t.context.page;
		await page.goto(`${t.context.serverUrl}/${testName}.html`);
		// If we made it this far, then the page successfully loaded.
		t.pass()
		});


		// TEST BUILDING BLOCKS
		@@ -179,0 +190,0 @@

Improved metrics