mirror of
https://github.com/meteor/meteor.git
synced 2026-05-02 03:01:46 -04:00
b3807831e4
* Update cordova-plugin-meteor-webapp to version 1.7.0.
Fixes #10516.
* Bump meteor-tool and webapp to a temporary 1.8.1-issue-10516.0 version.
I attempted to publish webapp@1.7.4-rc.0 with @rj-david's changes from
https://github.com/meteor/cordova-plugin-meteor-webapp/pull/78 to verify
that they fix #10516, but prerelease versions like 1.7.4-rc.0 are not
compatible with non-prerelease core package constraints like ~1.7.3 (which
desugars to >=1.7.3 <1.8.0), as explained by this comment in the semver
source code: 5fb517b290/semver.js (L1246-L1250)
While this behavior was somewhat surprising to me, I haven't come up with
a way to fix it without accidentally allowing any prerelease version of
core Meteor packages to be installed in applications using an official
(non-prerelease) version of Meteor.
Instead, we can just cut a temporary prerelease version of Meteor itself.
If that fixes the problem, then we can publish webapp@1.7.4 safely,
without actually publishing a Meteor 1.8.1.1 release just for this.
* Update webapp to version 1.7.4 (without -issue-10516.0 suffix).
65 lines
1.9 KiB
JavaScript
65 lines
1.9 KiB
JavaScript
Package.describe({
|
|
summary: "Serves a Meteor app over HTTP",
|
|
version: '1.7.4'
|
|
});
|
|
|
|
Npm.depends({"basic-auth-connect": "1.0.0",
|
|
"cookie-parser": "1.4.3",
|
|
connect: "3.6.5",
|
|
compression: "1.7.1",
|
|
errorhandler: "1.5.0",
|
|
parseurl: "1.3.2",
|
|
send: "0.16.1",
|
|
"stream-to-string": "1.1.0",
|
|
"qs-middleware": "1.0.3",
|
|
useragent: "2.3.0"});
|
|
|
|
Npm.strip({
|
|
multiparty: ["test/"],
|
|
useragent: ["test/"]
|
|
});
|
|
|
|
Cordova.depends({
|
|
'cordova-plugin-whitelist': '1.3.3',
|
|
'cordova-plugin-wkwebview-engine': '1.1.4',
|
|
'cordova-plugin-meteor-webapp': '1.7.0'
|
|
});
|
|
|
|
Package.onUse(function (api) {
|
|
api.use('ecmascript');
|
|
api.use([
|
|
'logging',
|
|
'underscore',
|
|
'routepolicy',
|
|
'modern-browsers',
|
|
'boilerplate-generator',
|
|
'webapp-hashing',
|
|
'inter-process-messaging',
|
|
], 'server');
|
|
|
|
// At response serving time, webapp uses browser-policy if it is loaded. If
|
|
// browser-policy is loaded, then it must be loaded after webapp
|
|
// (browser-policy depends on webapp). So we don't explicitly depend in any
|
|
// way on browser-policy here, but we use it when it is loaded, and it can be
|
|
// loaded after webapp.
|
|
api.mainModule('webapp_server.js', 'server');
|
|
api.export('WebApp', 'server');
|
|
api.export('WebAppInternals', 'server');
|
|
api.export('main', 'server');
|
|
|
|
api.mainModule('webapp_client.js', 'client');
|
|
api.export('WebApp', 'client');
|
|
|
|
api.mainModule('webapp_cordova.js', 'web.cordova');
|
|
});
|
|
|
|
Package.onTest(function (api) {
|
|
api.use(['tinytest', 'ecmascript', 'webapp', 'http', 'underscore']);
|
|
api.addFiles('webapp_tests.js', 'server');
|
|
api.addFiles('webapp_client_tests.js', 'client');
|
|
api.addFiles('socket_file_tests.js', 'server');
|
|
|
|
api.addAssets('modern_test_asset.js', 'web.browser');
|
|
api.addAssets('legacy_test_asset.js', 'legacy');
|
|
});
|