Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@jsenv/url-meta

Package Overview
Dependencies
Maintainers
0
Versions
32
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@jsenv/url-meta - npm Package Versions

124

5.2.2

Diff

dmail
published 5.2.1 •

dmail
published 5.2.0 •

dmail
published 5.1.1 •

dmail
published 5.1.0 •

dmail
published 5.0.0 •

Changelog

Source

35.0.0

  • Introduce @jsenv/test and update how runtimes are configured

version 34.0

import { executeTestPlan, chromium } from "@jsenv/core";

await executeTestPlan({
  testPlan: {
    "**/*.test.html": {
      runtime: chromium,
      runtimeParams: { headful: true },
    },
  },
});

version 35.0

import { executeTestPlan, chromium } from "@jsenv/test";

await executeTestPlan({
  testPlan: {
    "**/*.test.html": {
      runtime: chromium({ headful: true }),
    },
  },
});
dmail
published 4.1.0 •

Changelog

Source

34.1.0

  • Update coverage behaviour
    • Instrument only _.js, _.jsx, _.ts, _.tsx
    • Move istanbul instrumentation from jsenv dev server to a playwright middleware
    • Make fallback on istanbul for coverage more explicit in the code
  • Remove first line break from logs during test execution
dmail
published 4.0.0 •

Changelog

Source

34.0.0

  • Test execution becomes compatible with any web server
    • Remove devServerOrigin, devServerModuleUrl
    • Introduce webServer: { origin, rootDirectoryUrl, moduleUrl }
  • Exclude some files from test plan by default
    • File inside node modules
    • File inside directory starting with a dot (like ".git/")
  • Update test execution logs
    • Less line breaks when completedExecutionAbbreviation is enabled
    • Pad execution number with 0 like "execution 01 of 10" instead of "execution 1 of 10"
  • Add edge and firefox version supporting import.meta.resolve
  • Add safari version supporting import maps
  • Change how server are stopped after test plan is done
dmail
published 3.0.0 •

Changelog

Source

33.0.0

  • testDirectoryUrl -> rootDirectoryUrl
dmail
published 2.0.0 •

Changelog

Source

32.0.0

  • Dev server is now designed to run on a directory containing only source files It's still possible to start dev server in a directory containing files that are not meant to be executed in the browser but this is no longer the recommended way to use it
  • Update startDevServer params
    • rootDirectoryUrl -> sourceDirectoryUrl
    • clientMainFileUrl -> sourceMainFilePath
  • Update build params
    • rootDirectoryUrl -> sourceDirectoryUrl
  • Update startBuildServer params
    • buildIndexPath -> buildMainFilePath
  • Update executeTestPlan params
    • rootDirectoryUrl -> testDirectoryUrl
    • Introduce devServerModuleUrl
  • executeTestPlan is now able to start dev server
  • executeTestPlan enforce testDirectoryUrl to be inside the sourceDirectoryUrl passed to dev server when tests are executed on browsers
  • Use node 19
SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc