view release on metacpan or search on metacpan
remove = Plack::Util
remove = Plack::Util::Accessor
[Prereqs / BuildRequires ]
-phase = build
-relationship = requires
ExtUtils::MakeMaker = 7.22
Module::Metadata = 1.000015
[Prereqs / DevelopRequires ]
-phase = develop
-relationship = requires
Test::CVE = 0.08
Software::Security::Policy::Individual = 0.10
; [EnsurePrereqsInstalled]
; :version = 0.003
; type = requires
; type = recommends
[SecurityPolicy]
-policy = Individual
timeframe = 2 weeks
view release on metacpan or search on metacpan
remove = Plack::Util
remove = Plack::Util::Accessor
[Prereqs]
-phase = test
-relationship = requires
Test::More = 1.302176 ;; Test2::API
[EnsurePrereqsInstalled]
:version = 0.003
type = requires
type = recommends
[GitHub::Meta]
repo = git@github.com:robrwo/Plack-Middleware-EmulateOPTIONS.git
view release on metacpan or search on metacpan
remove = Plack::Util
remove = Plack::Util::Accessor
[Prereqs]
-phase = test
-relationship = requires
Cache::FastMmap = 1.52
[EnsurePrereqsInstalled]
:version = 0.003
type = requires
type = recommends
[GitHub::Meta]
repo = git://github.com/robrwo/Plack-Middleware-Greylist.git
view release on metacpan or search on metacpan
[RecommendedPrereqs]
[AutoPrereqs]
[Prereqs / TestRequires]
-phase = test
-relationship = requires
Test::Vars = 0.015
[Prereqs / DevelopRequires ]
-phase = develop
-relationship = requires
Test::CPAN::Changes = 0
Software::Security::Policy::Individual = 0.10
[EnsurePrereqsInstalled]
:version = 0.003
type = requires
type = recommends
[SecurityPolicy]
-policy = Individual
timeframe = 2 weeks
view release on metacpan or search on metacpan
remove = Plack::Util
remove = Plack::Util::Accessor
[Prereqs / BuildRequires ]
-phase = build
-relationship = requires
ExtUtils::MakeMaker = 7.22
Module::Metadata = 1.000015
[Prereqs / DevelopRequires ]
-phase = develop
-relationship = requires
Software::Security::Policy::Individual = 0.10
Test::CVE = 0.11
Test2::Require::AuthorTesting = 0
; [EnsurePrereqsInstalled]
; :version = 0.003
; type = requires
; type = recommends
[SecurityPolicy]
; authordep Software::Security::Policy::Individual
-policy = Individual
view release on metacpan or search on metacpan
remove = Plack::Util
remove = Plack::Util::Accessor
[Prereqs]
-phase = develop
-relationship = requires
Test::Vars = 0.015
[EnsurePrereqsInstalled]
:version = 0.003
type = requires
type = recommends
[Git::CheckFor::MergeConflicts]
[GitHub::Meta]
view release on metacpan or search on metacpan
[AutoPrereqs]
;; [PrereqsClean]
[EnsurePrereqsInstalled]
:version = 0.003
type = requires
type = recommends
[GitHub::Meta]
repo = git://github.com/robrwo/Plack-Middleware-TimeOverHTTPS.git
view release on metacpan or search on metacpan
remove = Plack::Util
remove = Plack::Util::Accessor
[Prereqs]
-phase = develop
-relationship = requires
Test::Vars = 0.015
[EnsurePrereqsInstalled]
:version = 0.003
type = requires
type = recommends
[GitHub::Meta]
repo = git://github.com/robrwo/Plack-Middleware-TrafficAdvice.git
view release on metacpan or search on metacpan
bin/playwright_server view on Meta::CPAN
#!/usr/bin/env node
"use strict";
// If we don't have this, we're done for
const { exit } = require('process');
const fs = require('fs');
const path = require('path');
const { env } = require('process');
module.paths.push( '/usr/local/lib/node_modules' );
// Assume their kit is good
require('uuid');
require('playwright');
require('express');
// Get what we actually want from our deps
const { v4 : uuidv4 } = require('uuid');
const { chromium, firefox, webkit, devices } = require('playwright');
const express = require('express');
const bodyParser = require('body-parser');
// Setup the max body size
// Stuff like this is why I don't usually use frameworks, just chunk it dawg
var MAX_REQUEST_SIZE = env.MAX_REQUEST_SIZE;
// Defines our interface
// let sharedir = require.resolve('playwright'); // api.json should be shipped with playwright itself
// var theFile = path.dirname(sharedir) + '/api.json';
// let rawdata = fs.readFileSync(theFile);
// This is automatically inserted via sed
let spec =
[{"name":"Accessibility","spec":[{"type":"text","text":"The Accessibility class provides methods for inspecting Chromium's accessibility tree. The accessibility tree is used by↵assistive technology such as [screen readers](https://en.wikipedia.org/...
function arr2hash (arr,primary_key) {
var inside_out = {};
for (var item of arr) {
inside_out[item.name] = item;
view release on metacpan or search on metacpan
; version_rel_day = 1
; version_rel_hour = 14
; version_rel_time_zone = Pacific/Auckland
; auto_prereqs_skip = File::Find
-phase = develop
-relationship = requires
Dist::Zilla::Plugin::Author::KENTNL::RecommendFixes = 0.004002
Dist::Zilla::Plugin::Author::KENTNL::TravisCI = 0.001002
Dist::Zilla::Plugin::Authority = 1.006
Dist::Zilla::Plugin::AutoPrereqs = 0
Dist::Zilla::Plugin::BumpVersionAfterRelease = 0
view release on metacpan or search on metacpan
lib/Pod/POM/Web/PSGI.pm view on Meta::CPAN
plackup -e 'require Pod::POM::Web::PSGI'
Load Pod::POM::Web as a PSGI application:
my $app = require Pod::POM::Web::PSGI;
=head1 DESCRIPTION
This is a wrapper for L<Pod::POM::Web> to transform it as a L<PSGI> application.
This allow then to integrate Pod::POM::Web in a bigger web application, by
view release on metacpan or search on metacpan
Makefile.PL view on Meta::CPAN
But, it's more interesting than that. You can load it with C<require>
and call C<arguments> to get the data structure it passes to
C<WriteMakefile>:
my $package = require '/path/to/Makefile.PL';
my $arguments = $package->arguments;
Note that C<require>-ing a file makes an entry in C<%INC> for exactly
that name. If you try to C<require> another file with the same name,
even from a different path, C<require> thinks it has already loaded
view release on metacpan or search on metacpan
remove = IO::Handle
remove = Module::Load
[EnsurePrereqsInstalled]
:version = 0.003
type = requires
type = recommends
[GitHub::Meta]
repo = git://github.com/bigpresh/Pod-Readme.git
view release on metacpan or search on metacpan
Makefile.PL view on Meta::CPAN
But, it's more interesting than that. You can load it with C<require>
and call C<arguments> to get the data structure it passes to
C<WriteMakefile>:
my $package = require '/path/to/Makefile.PL';
my $arguments = $package->arguments;
Note that C<require>-ing a file makes an entry in C<%INC> for exactly
that name. If you try to C<require> another file with the same name,
even from a different path, C<require> thinks it has already loaded
view release on metacpan or search on metacpan
lib/Pod/Weaver/PluginBundle/Author/KENTNL.pm view on Meta::CPAN
-~- Inherited from @Author::KENTNL::Collectors -~-
; command[].default = [ required function attr method pfunction pattr pmethod ]
; command[].entry_type[0] = KNOWNCOMMANDNAME
; command[].entry_type[1] = COMMANDNAME = DESCRIPTION
; KNOWNCOMMANDNAME.enums =
; = required ; REQUIRED METHODS
; = function ; FUNCTIONS
; = method ; METHODS
; = attr ; ATTRIBUTES
; = cattr ; ATTRIBUTES / CONSTRUCTOR ARGUMENTS
; = pfuncton ; PRIVATE FUNCTIONS
view release on metacpan or search on metacpan
Makefile.PL view on Meta::CPAN
But, it's more interesting than that. You can load it with C<require>
and call C<arguments> to get the data structure it passes to
C<WriteMakefile>:
my $package = require '/path/to/Makefile.PL';
my $arguments = $package->arguments;
Note that C<require>-ing a file makes an entry in C<%INC> for exactly
that name. If you try to C<require> another file with the same name,
even from a different path, C<require> thinks it has already loaded
view release on metacpan or search on metacpan
Makefile.PL view on Meta::CPAN
But, it's more interesting than that. You can load it with C<require>
and call C<arguments> to get the data structure it passes to
C<WriteMakefile>:
my $package = require '/path/to/Makefile.PL';
my $arguments = $package->arguments;
Note that C<require>-ing a file makes an entry in C<%INC> for exactly
that name. If you try to C<require> another file with the same name,
even from a different path, C<require> thinks it has already loaded
view release on metacpan or search on metacpan
lib/QBit/Validator/Type/hash.pm view on Meta::CPAN
return 0;
}
}
#TODO: implement method _exists
# defined = required
sub fields {
my ($qv, $fields, $template) = @_;
my $parent = $qv->parent // $qv;
view release on metacpan or search on metacpan
lib/Qgoda/Command/Javascript.pm view on Meta::CPAN
are accepted by Duktape!
Qgoda, however, implements a module resolver so that you can use constructs
like:
const _ = require('lodash');
The module is resolved in the same way that NodeJS would resolve it.
See the option I<--global> below for more information.
=head1 OPTIONS
view release on metacpan or search on metacpan
foreach(@files) {
my %test = ( file => $_ );
logger("loading $_... ");
$test{cb} = require $_;
logger("done\n");
push(@buf, \%test);
}
view release on metacpan or search on metacpan
;version_rel_month = 12
;version_rel_day = 25
;version_rel_hour = 13
;version_rel_time_zone = Pacific/Auckland
-phase = develop
-relationship = requires
Dist::Zilla::Plugin::Author::KENTNL::CONTRIBUTING = 0.001003
Dist::Zilla::Plugin::Author::KENTNL::RecommendFixes = 0.004002
Dist::Zilla::Plugin::Author::KENTNL::TravisCI = 0.001002
Dist::Zilla::Plugin::Authority = 1.006
Dist::Zilla::Plugin::AutoPrereqs = 0
view release on metacpan or search on metacpan
lib/Repo/html/requires_tree_html.template view on Meta::CPAN
var div = d3.select(document.getElementById( 'front_wrapper' )).append("div")
.attr("class", "tree-tooltip")
.style("opacity", 0);
d3.json("@JSON_DATA_FILE@", function(error, requires) {
root = requires;
root.x0 = height / 2;
root.y0 = 0;
function collapse(d) {
if (d.children) {
view release on metacpan or search on metacpan
lib/Require/Util.pm view on Meta::CPAN
if (try_require "Foo::Bar") {
# use Foo::Bar's function
}
my $modname = require_any "Foo::Bar", "Baz/Qux.pm", "Quux";
=head1 DESCRIPTION
B<EXPERIMENTAL.>
lib/Require/Util.pm view on Meta::CPAN
=head2 require_any
Usage:
my $res = require_any $modname1, $modname2, ...;
Example:
my $res = require_any "Foo::Bar", "Baz/Qux.pm";
Require modules listed as arguments, stopping after the first success. If all
modules cannot be loaded, will die. Module name can be specified as C<Foo::Bar>
syntax or as C<Foo/Bar.pm> syntax. Unlike C<require()> which just returns true,
upon success the function will return the module name that gets loaded.
view release on metacpan or search on metacpan
Makefile.PL view on Meta::CPAN
But, it's more interesting than that. You can load it with C<require>
and call C<arguments> to get the data structure it passes to
C<WriteMakefile>:
my $package = require '/path/to/Makefile.PL';
my $arguments = $package->arguments;
Note that C<require>-ing a file makes an entry in C<%INC> for exactly
that name. If you try to C<require> another file with the same name,
even from a different path, C<require> thinks it has already loaded
view release on metacpan or search on metacpan
lib/Rewire/Engine.pm view on Meta::CPAN
# FUNCTIONS
# returns the json-schema-based engine ruleset
fun ruleset() {
state $ruleset = require Rewire::Ruleset;
}
# returns context closure
fun context() {
my $cache = {};
view release on metacpan or search on metacpan
desc 'Full server deploy: prepare_node + install_server + Cilium';
task 'server', sub {
my ($params) = @_;
my $distribution = $params->{distribution} // 'rke2';
die "token= required\n" unless $params->{token};
my %opts = (
distribution => $distribution,
token => $params->{token},
);
desc 'Full agent deploy: prepare_node + join cluster';
task 'agent', sub {
my ($params) = @_;
my $distribution = $params->{distribution} // 'rke2';
die "token= required\n" unless $params->{token};
die "server= required\n" unless $params->{server};
my %opts = (
distribution => $distribution,
token => $params->{token},
server => $params->{server},
view release on metacpan or search on metacpan
remove = strict
remove = warnings
[EnsurePrereqsInstalled]
:version = 0.003
type = requires
type = recommends
[GitHub::Meta]
repo = git://github.com/robrwo/Robots-Validate.git
view release on metacpan or search on metacpan
vendor/rocksdb/tools/rdb/rdb view on Meta::CPAN
#!/usr/bin/env bash
node -e "RDB = require('./build/Release/rdb').DBWrapper; console.log('Loaded rocksdb in variable RDB'); repl = require('repl').start('> ');"
view release on metacpan or search on metacpan
Makefile.PL view on Meta::CPAN
But, it's more interesting than that. You can load it with C<require>
and call C<arguments> to get the data structure it passes to
C<WriteMakefile>:
my $package = require '/path/to/Makefile.PL';
my $arguments = $package->arguments;
Note that C<require>-ing a file makes an entry in C<%INC> for exactly
that name. If you try to C<require> another file with the same name,
even from a different path, C<require> thinks it has already loaded
view release on metacpan or search on metacpan
lib/SPVM/Builder/src/spvm_op.c view on Meta::CPAN
}
}
args_length++;
}
method->args_length = args_length;
method->required_args_length = required_args_length;
}
// Variable declarations of arguments
SPVM_OP* op_arg = op_args->first;
while ((op_arg = SPVM_OP_sibling(compiler, op_arg))) {