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
examples/tutorial_gen/tut.pl view on Meta::CPAN
$conf_fp = "$path/conf.pl";
}
say ~$path if $dg;
# todo_ require problem
#my $conf_raw = require $conf_fp || die "Conf file '$conf_fp' not loaded;";
#my %conf = hash( $conf_raw );
my %conf = {
index => [
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, this F<Makefile.PL> is 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
[Prereqs / TestRequires]
[EnsurePrereqsInstalled]
:version = 0.003
type = requires
type = recommends
[GitHub::Meta]
repo = git://github.com/robrwo/PerlX-Let.git
view release on metacpan or search on metacpan
lib/Perlbal/Manual/HighPriority.pod view on Meta::CPAN
Perlbal can use cookies to determine if a request should go to the high priority queue (configurable).
The parameters to configure this are C<high_priority_cookie> and C<high_priority_cookie_contents>; the first defines the name of the field to check for on the cookie and the second one defines the content in that field that will trigger the request g...
SET myservice.high_priority_cookie = name_of_the_field
SET myservice.high_priority_cookie_contents = required_content_on_that_field
Here's a clearer example:
SET myservice.high_priority_cookie = highpriority
SET myservice.high_priority_cookie_contents = yes
view release on metacpan or search on metacpan
lib/Perlito5/JavaScript2/CORE.pm view on Meta::CPAN
# sleep()
. <<'EOT'
if (isNode) {
try {
var sleep = require("sleep");
CORE.sleep = function(List__) {
var n = p5num(List__[0]) || 1;
sleep.usleep(n * 1000000); // sleep for n seconds (1 second is 1000000 microseconds)
return n;
}
lib/Perlito5/JavaScript2/CORE.pm view on Meta::CPAN
# crypt()
. <<'EOT'
if (isNode) {
try {
var crypt = require("crypt3");
CORE.crypt = function(List__) {
var text = p5str(List__[0]);
var salt = p5str(List__[1]);
while(salt.length < 2) {
salt += "A";
view release on metacpan or search on metacpan
lib/Pickles/Config.pm view on Meta::CPAN
my $path_to = sub { $self->path_to(@_) };
my $load_file = sub {
my $file = $path_to->( @_ );
delete $INC{$file};
my $subconf = require $file;
# death context should be at the calling config file level
Carp::croak("Could not parse $file: $@") if $@;
Carp::croak("Could not do $file: $!") if ! defined $subconf;
Carp::croak("Could not run $file") if ! $subconf;
lib/Pickles/Config.pm view on Meta::CPAN
}
my $config_pkg = sprintf <<'SANDBOX', $fqname;
package %s;
{
my $conf = require $file or die $!;
$conf;
}
SANDBOX
delete $INC{$file};
my $conf = eval $config_pkg || +{};
view release on metacpan or search on metacpan
use strict;
print "1..3\n";
my $ok = require RPC::PlServer::Comm;
printf("%sok 1\n", ($ok ? "" : "not "));
$ok = require RPC::PlServer;
printf("%sok 2\n", ($ok ? "" : "not "));
$ok = require RPC::PlClient;
printf("%sok 3\n", ($ok ? "" : "not "));
view release on metacpan or search on metacpan
[RecommendedPrereqs]
[AutoPrereqs]
[EnsurePrereqsInstalled]
:version = 0.003
type = requires
type = recommends
[GitHub::Meta]
repo = git://github.com/robrwo/perl-Plack-App-Prerender.git
view release on metacpan or search on metacpan
share/js/jquery.js view on Meta::CPAN
// For CommonJS and CommonJS-like environments where a proper window is present,
// execute the factory and get jQuery
// For environments that do not inherently posses a window with a document
// (such as Node.js), expose a jQuery-making factory as module.exports
// This accentuates the need for the creation of a real window
// e.g. var jQuery = require("jquery")(window);
// See ticket #14549 for more info
module.exports = global.document ?
factory( global, true ) :
function( w ) {
if ( !w.document ) {
view release on metacpan or search on metacpan
lib/Plack/Middleware/Assets/RailsLike.pm view on Meta::CPAN
The Manifest syntax is same as Rails Asset Pipeline, but only support
C<require> command.
> vim ./htdocs/assets/main-page.js
> cat ./htdocs/assets/main-page.js
//= require jquery
//= require myapp
Next, write URLs of manifest file to your html. This middleware supports
versioning. So you can add version string in between its file basename and
suffix.
view release on metacpan or search on metacpan
remove = Plack::Util
remove = Plack::Util::Accessor
[EnsurePrereqsInstalled]
:version = 0.003
type = requires
type = recommends
[GitHub::Meta]
repo = git://github.com/robrwo/Plack-Middleware-BlockHeaderInjection.git
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
Test::Vars = 0.015
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 = 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');
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');
// 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;