view release on metacpan or search on metacpan
lib/Memcached/libmemcached/API.pm view on Meta::CPAN
libmemcached_constants
libmemcached_tags
);
# load hash of libmemcached functions created by Makefile.PL
my $libmemcached_funcs = require "Memcached/libmemcached/func_hash.pl";
die "Memcached/libmemcached/func_hash.pl failed sanity check"
unless ref $libmemcached_funcs eq 'HASH'
and keys %$libmemcached_funcs > 20;
# extra functions provided by Memcached::libmemcached
lib/Memcached/libmemcached/API.pm view on Meta::CPAN
grep { $funcs{$_} } sort keys %funcs;
};
# load hash of libmemcached functions created by Makefile.PL
my $libmemcached_consts = require "Memcached/libmemcached/const_hash.pl";
die "Memcached/libmemcached/const_hash.pl failed sanity check"
unless ref $libmemcached_consts eq 'HASH'
and keys %$libmemcached_consts > 20;
our @libmemcached_consts = sort keys %$libmemcached_consts;
view release on metacpan or search on metacpan
; version_rel_day = 22
; version_rel_hour = 5
; 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
; version_rel_day = 22
; version_rel_hour = 5
; 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
[Prereqs]
Moo = 1.000008
[Prereqs / developrequires]
-phase = develop
-relation = requires
MetaPOD::Format::JSON = 0.3.0
view release on metacpan or search on metacpan
bin/makeMicroarrayDataset.pl view on Meta::CPAN
$0 -file <file/name> -name <intended/dataset/name> [-dataout <repository_directory> -imageout <image directory> -contrast <float> -colorscheme <rg|yb> -corrcutoff <float> -verbose]
-----------------------------------------------------------------------------
-file = required input file (currently only '.cdt' files supported)
-name = required dataset name to be created
(may be delimited by slashes(/) to imply hierarchy)
-rootpath = required root directory, under which must exist html
and data directories
-contrast = optional contrast value for the generated images
(defaults to 4, As the data are expected to be in
log base 2, this corresponds to a 16-fold change as
view release on metacpan or search on metacpan
; version_rel_day = 31
; version_rel_hour = 6
; 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
; version_rel_month = 3
; version_rel_day = 22
; version_rel_hour = 13
; version_rel_time_zone = Pacific/Auckland
-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
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
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
corpus/state_require.pm view on Meta::CPAN
sub do_it {
state $rc = require ConfigReader::Simple;
}
my $rc = require Mojo::Util;
my %data = (
require => 42, # Should not report '=>'.
);
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/Module/Load/Conditional.pm view on Meta::CPAN
}
}
=back
=head2 @list = requires( MODULE );
C<requires> can tell you what other modules a particular module
requires. This is particularly useful when you're intending to write
a module for public release and are listing its prerequisites.
view release on metacpan or search on metacpan
share/template/Makefile.PL view on Meta::CPAN
abstract '[% abstract %]';
version '[% version %]';
license '[% license %]';
perl_version '[% perl_version %]';
[% FOR r = requires -%]
[% module = r.keys.0 -%]
requires '[% module %]' => '[% r.$module %]';
[% END -%]
[% IF install_script -%]
view release on metacpan or search on metacpan
[Prereqs / DevelopRequires]
Test::Builder = 0.90 ; for is_passing
[DynamicPrereqs]
:version = 0.016
-raw = requires('IO::Scalar') if "$]" < '5.008';
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/Module/Release/VerifyGPGSignature.pm view on Meta::CPAN
=over 4
=cut
sub _get_file_pairs ( $self ) {
state $rc = require Getopt::Long;
my $key = _key($self);
my $string = $self->config->$key();
my( $ret, $args ) = Getopt::Long::GetOptionsFromString($string);
view release on metacpan or search on metacpan
lib/Module/Release.pm view on Meta::CPAN
Changes file.
=cut
sub get_release_date {
state $rc = require Time::Piece;
return Time::Piece->gmtime->datetime . 'Z';
}
=item run
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/Mojo/Phantom.pm view on Meta::CPAN
has template => <<'TEMPLATE';
% my ($self, $url, $js) = @_;
// Setup perl function
function perl() {
var system = require('system');
var args = Array.prototype.slice.call(arguments);
system.stdout.writeLine(JSON.stringify(args));
system.stdout.writeLine('<%== $self->sep %>');
system.stdout.flush();
}
lib/Mojo/Phantom.pm view on Meta::CPAN
domain: '<%== $cookie->domain || $self->base->host %>',
}) || perl.diag('Failed to import cookie <%== $name %>');
% }
// Requst page and inject user-provided javascript
var page = require('webpage').create();
page.onError = onError;
% if($self->note_console) {
// redirect browser console log to TAP
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/Mojo/Base/Che.pm view on Meta::CPAN
#~ push @libs, $it # abs lib
#~ and next
#~ if $it =~ m'^/';
#~ $findbin ||= require FindBin && $FindBin::Bin;# relative lib
#~ push @libs, $findbin.'/'.$it;
#~ }
#~ my @ok_libs = grep { my $lib = $_; not scalar grep($lib eq $_, @INC) } @libs
#~ if @libs;
view release on metacpan or search on metacpan
lib/Mojolicious/Plugin/AssetPack/Pipe/VueTemplateCompiler.pm view on Meta::CPAN
__DATA__
@@ vue-template-compiler.js
#!/usr/bin/env node
"use strict"
let fs = require("fs");
let stdinBuffer = fs.readFileSync(0); // STDIN_FILENO = 0
const compiler = require('vue-template-compiler');
const util = require('@vue/component-compiler-utils');
///et c = compiler.compile(stdinBuffer.toString());
///let errs = c.errors;
view release on metacpan or search on metacpan
lib/Mojolicious/Plugin/AssetPack/Pipe/RollupJs.pm view on Meta::CPAN
#!/usr/bin/env node
"use strict"
const globals = __GLOBALS__;
const external = __EXTERNAL__;
const rollup = require("rollup");
const stdout = process.stdout;
function _interopDefault(i) {
return i && typeof i === "object" && "default" in i ? i["default"] : i;
}
view release on metacpan or search on metacpan
lib/Mojolicious/Plugin/DevexpressHelpers/Helpers.pm view on Meta::CPAN
in your template:
<body>
...
%= require_asset 'MyScript.js'
...
</body>
in your layout:
<head>
...
%= required_assets
...
</head>
=head2 required_assets
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/Mojolicious/Plugin/Materialize/js/materialize.js view on Meta::CPAN
// Check for jQuery.
if (typeof(jQuery) === 'undefined') {
var jQuery;
// Check if require is a defined function.
if (typeof(require) === 'function') {
jQuery = $ = require('jquery');
// Else use the dollar sign alias.
} else {
jQuery = $;
}
}
view release on metacpan or search on metacpan
share/public/revealjs/plugin/markdown/markdown.js view on Meta::CPAN
* markdown inside of presentations as well as loading
* of external markdown documents.
*/
(function( root, factory ) {
if (typeof define === 'function' && define.amd) {
root.marked = require( './marked' );
root.RevealMarkdown = factory( root.marked );
root.RevealMarkdown.initialize();
} else if( typeof exports === 'object' ) {
module.exports = factory( require( './marked' ) );
} else {
view release on metacpan or search on metacpan
[Prereqs]
Mojolicious = 0
[EnsurePrereqsInstalled]
:version = 0.003
type = requires
type = recommends
[Git::CheckFor::MergeConflicts]
[GitHub::Meta]
view release on metacpan or search on metacpan
lib/Mojo/Alien/rollup.pm view on Meta::CPAN
=cut
__DATA__
@@ include/core.js
const commonjs = require('@rollup/plugin-commonjs');
const {nodeResolve} = require('@rollup/plugin-node-resolve');
module.exports = function(config) {
config.plugins.push(nodeResolve());
config.plugins.push(commonjs());
};
@@ include/css.js
const postcss = require('rollup-plugin-postcss');
module.exports = function(config) {
config.plugins.push(postcss({
extract: true,
plugins: [
lib/Mojo/Alien/rollup.pm view on Meta::CPAN
require('cssnano')(),
],
}));
};
@@ include/eslint.js
const eslint = require('@rollup/plugin-eslint');
module.exports = function(config, {isDev}) {
if (!isDev) return;
config.plugins.push(eslint({
exclude: ['node_modules/**', '**/*.css', '**/*.sass'],
fix: process.env.ESLINT_FIX ? true : false,
}));
}
@@ include/js.js
const {babel} = require('@rollup/plugin-babel');
const {terser} = require('rollup-plugin-terser');
module.exports = function(config, {isDev}) {
config.plugins.push(babel({
babelHelpers: 'runtime',
extensions: ['.html', '.js', '.mjs'],
lib/Mojo/Alien/rollup.pm view on Meta::CPAN
}));
if (!isDev) config.plugins.push(terser());
}
@@ include/sass.js
const postcss = require('rollup-plugin-postcss');
module.exports = function(config) {
config.plugins.push(postcss({extract: true, plugins: [
require('@csstools/postcss-sass')(),
require('postcss-preset-env')(),
require('cssnano')(),
]}));
};
@@ include/svelte.js
const svelte = require('rollup-plugin-svelte');
module.exports = function(config) {
config.plugins.push(svelte({}));
};
@@ rollup.config.js
const fs = require('fs');
const pkg = require('./package.json');
const path = require('path');
const assetsDir = process.env.ROLLUP_ASSETS_DIR || path.resolve(__dirname, 'assets');
const isDev = process.env.NODE_ENV !== 'production';
const outDir = process.env.ROLLUP_OUT_DIR || path.resolve(__dirname, 'dist');
const ts = parseInt((new Date().getTime() / 1000), 10).toString(16);