BrianMulhall
a67e25a834
pared down the number of test cases that we need to maintain moving forward
2020-03-20 17:24:03 -05:00
Brian Mulhall
065e3c0b47
update the test cases to verify that terser is in fact handling the test cases we are assuming they can handle
2020-03-18 18:21:16 -05:00
Brian Mulhall
5b1445bd16
Merge branch 'devel' into minifier_js_update
2020-03-16 19:37:05 -05:00
Brian Mulhall
3221cc472d
updated the markdown file to better document this package
2020-03-16 17:35:54 -05:00
Brian Mulhall
e56102c8f7
cleaning up the code a bit more
2020-03-16 16:20:57 -05:00
Brian Mulhall
df023e217d
refactoring this code to minimize the diff during a pull request
2020-03-16 13:20:35 -05:00
Brian Mulhall
2987fc932b
updating the error handling code
2020-03-16 13:11:32 -05:00
Brian Mulhall
6f92161a36
added a test case that exercises when terser fails and babel-minify is used as a fail safe
2020-03-16 13:10:07 -05:00
Brian Mulhall
d4b189f80b
cleaning up the code a bit before i submit the pull request
2020-03-16 11:38:37 -05:00
filipenevola
17136ff79a
Updates Roadmap and History with 1.10.1
2020-03-16 12:31:04 -03:00
Brian Mulhall
cc0d399169
adding additional test cases for classes and to exercise the keep_numbers setting a bit more
2020-03-15 10:40:26 -05:00
Brian Mulhall
b2458e1f1c
leave settings as they were originally so as to not introduce too much change that could effect our ability to test this set of changes
2020-03-14 20:11:55 -05:00
Brian Mulhall
60cbc082ef
update the version of the standard-minifier-js package from 2.6.0 to 2.6.1
2020-03-14 18:38:06 -05:00
Brian Mulhall
dcf1afbd64
add in some settings that while they are the default values Terser use out of the box, it will help to document what settings we are using to any developer reading the code
2020-03-14 18:37:32 -05:00
Brian Mulhall
d310e38574
updating the README.md documentation file
2020-03-14 18:32:38 -05:00
Brian Mulhall
b38abd9f45
adding more test cases for terser compress settings
2020-03-14 18:15:44 -05:00
Brian Mulhall
dd822d2cdb
update terser from 4.4.0 to 4.6.6 and then bump up the package version from 2.6.0 to 2.6.1
2020-03-14 15:45:36 -05:00
Brian Mulhall
96613f3103
updated the test cases to include a test for the keep_inifinty setting
2020-03-14 15:44:25 -05:00
Brian Mulhall
6924de02fa
updating the test cases for the minifier-js package
2020-03-14 15:27:47 -05:00
Brian Mulhall
93a9cf9a63
updating the class defintion to use the newer class syntax
2020-03-14 14:03:26 -05:00
Brian Mulhall
615e2a65af
updating the standard-minifier-js package to use more modern syntax and to correct and outdated comment
2020-03-14 12:43:20 -05:00
Brian Mulhall
cc4b6d81fe
updating the minifier-js to modernize it's syntax and review and update it configuration. The configuration options and settings are also documented as to why and how they are being set so future developers will understand why it is configured as it is
2020-03-14 12:42:20 -05:00
Brian Mulhall
783a9c7ecb
updating the minifier-js package to include test cases
2020-03-14 12:40:31 -05:00
Ben Newman
80359f0b2d
Merge branch 'master' into devel
2020-03-12 18:39:41 -04:00
Ben Newman
0835462b55
Merge pull request #10861 from meteor/release-1.10
...
Release 1.10
2020-03-12 18:38:56 -04:00
Ben Newman
d274d8d7ef
Work around bizarre SQLite dynamic type conversion behavior.
...
SQLite has a worse-is-better philosophy about automatically converting
between different data types, such as strings and floating point numbers:
https://www.sqlite.org/quirks.html#flexible_typing
This means querying for the string "1.10" in a given column can return
rows where the column is actually the string "1.1", since SQLite imagines
you might be talking about the number 1.1, rather than the string you
actually requested.
This "feature" became a problem for Meteor after we published Meteor 1.10,
which caused SQLite to return multiple rows for the getReleaseVersion
query, including both Meteor 1.10 and Meteor 1.1 (which is ancient, from
March 2015).
While this behavior seems completely indefensible, the SQLite
documentation clearly does not consider it a bug, which forces us to work
around the consequences by double-checking the queried results with the
filterExactRows helper function.
2020-03-12 18:07:39 -04:00
filipenevola
88d017137c
Bump package versions for 1.10.1 release
release/METEOR@1.10.1
2020-03-12 17:17:23 -03:00
filipenevola
39e57ecd79
Bump package versions for the official 1.10 release. 🎉
2020-03-12 14:29:56 -03:00
filipenevola
12ee7d37af
Bump package versions for 1.10.0-rc.5 release
release/METEOR@1.10-rc.5
2020-03-11 23:02:39 -03:00
filipenevola
e4fc3ccbcf
Documents the new command to ensure cordova dependencies are installed
2020-03-11 23:01:31 -03:00
Filipe Névola
5fb2f341f3
Merge pull request #10963 from meteor/fix-first-time-cordova-lib-installation
...
Stop calling moduleDoesResolve before installing Cordova npm deps.
2020-03-11 22:52:44 -03:00
Ben Newman
2b8834e92e
Stop calling moduleDoesResolve before installing Cordova npm deps.
...
This fixes the bug where commands like `meteor add-platform ios` would
fail the first time with an error that cordova-lib could not be found,
even though we attempt to install the necessary packages if they have not
already been installed.
To make a very long story short, calling moduleDoesResolve before
installing dependencies like cordova-lib was causing Node.js to cache the
_absence_ of cordova-lib/package.json permanently in the new
packageJsonCache, which cannot be invalidated or cleared by user code:
f8f20892e9/lib/internal/modules/cjs/loader.js (L245-L255)
Although we could potentially propose a change to Node to allow the
packageJsonCache to be invalidated, a more immediate solution is simply to
avoid calling moduleDoesResolve when there's any chance the module will
not resolve. Because we still want to avoid repeatedly installing Cordova
dependencies every time we run a Cordova command, we instead check whether
the necessary dependencies are installed by examining the file system.
2020-03-11 18:01:33 -04:00
filipenevola
824b247daa
Adds a new command to ensure cordova dependencies are installed
2020-03-11 17:59:56 -03:00
filipenevola
4997c76989
Removes unnecessary code (protect-string-proto.js) as Cordova 9 is not using shelljs anymore and also some unused imports
2020-03-11 17:59:25 -03:00
filipenevola
8822ce987e
Merge branch 'devel' into release-1.10
...
# Conflicts:
# packages/meteor-tool/package.js
# packages/npm-mongo/package.js
# scripts/admin/meteor-release-experimental.json
2020-03-09 22:48:17 -04:00
filipenevola
a8b31bc578
Merge branch 'master' into devel
...
# Conflicts:
# History.md
# packages/npm-mongo/.npm/package/npm-shrinkwrap.json
# packages/npm-mongo/package.js
2020-03-09 22:47:26 -04:00
Filipe Névola
b7a8b1ed44
Merge pull request #10961 from meteor/mongodb-fix-driver
...
Release 1.9.3
2020-03-09 22:44:09 -04:00
filipenevola
e3174c9735
Updates npm-mongo npm-shrinkwrap.json
2020-03-09 19:09:32 -04:00
filipenevola
354e24b3f6
Bump package versions for 1.9.3 release 🎉
release/METEOR@1.9.3
2020-03-09 18:55:24 -04:00
filipenevola
830a726d11
Updates History explaining the change on Swift version
2020-03-06 13:10:55 -04:00
filipenevola
5e5c75b36b
Bump package versions for 1.10-rc.4 release
2020-03-06 13:10:35 -04:00
filipenevola
65fc649375
Bump npm-mongo package version to avoid conflicts with Meteor 1.9.3
2020-03-06 10:31:40 -04:00
filipenevola
ae503c5727
Use -quiet option for iOS to avoid unnecessary messages
2020-03-06 10:25:18 -04:00
filipenevola
feebaabc95
Fixes SWIFT_VERSION error
2020-03-06 10:24:56 -04:00
filipenevola
92d0674469
Bump package versions for 1.9.3-rc.0 release
release/METEOR@1.9.3-rc.0
2020-03-05 20:23:13 -04:00
filipenevola
71ae51a277
Updates mongodb driver to 3.5.4
2020-03-05 20:22:23 -04:00
filipenevola
975759f6aa
WKWebViewOnly is set by default now as true and updates cordova-plugin-meteor-webapp to 1.9.0 that is compatible with Swift 5
2020-03-04 17:11:41 -04:00
Filipe Névola
629b3670b2
Merge pull request #10958 from StorytellerCZ/devel
...
Migrations steps for 1.10 MongoDB `Unexpected exit code 62`
2020-03-04 16:45:09 -04:00
Jan Dvorak
82d340921c
Update History.md
...
Co-Authored-By: Christian Klaussner <christian@klaussner.me >
2020-03-03 21:06:19 +09:00
Jan Dvorak
2f5459c267
Migrations steps for 1.10 MongoDB Unexpected exit code 62
...
Add migrations steps in case of `Unexpected mongo exit code 62.`
2020-03-03 09:07:07 +09:00