Michael Scharf comments

Results 21 comments of


                                            Michael Scharf

Memory leak in long running single test

see https://github.com/cypress-io/cypress/issues/1906#issuecomment-502465837

While minifying app code: `Unexpected token, expected ":" (1056:150096)`

As hack, I have removed the minifier form the app with `meteor remove standard-minifier-js`. This fixes the build.

While minifying app code: `Unexpected token, expected ":" (1056:150096)`

It is still an issue :-(.

While minifying app code: `Unexpected token, expected ":" (1056:150096)`

I found the cause: [After the release of v1.0.0-rc.11, Module parse failed: Unexpected token occurs #2545](https://github.com/cheeriojs/cheerio/issues/2545). To reproduce, just add a newer version of `cheerio` and `require('cheerio');` somewhere. See: https://github.com/cheeriojs/cheerio/issues/2545#issuecomment-1183477852...

While minifying app code: `Unexpected token, expected ":" (1056:150096)`

use https://www.npmjs.com/package/@babel/plugin-transform-export-namespace-from

While minifying app code: `Unexpected token, expected ":" (1056:150096)`

Unfortunately adding `npm install -D @babel/plugin-transform-export-namespace-from` and adding the following `.babelrc` ``` { "plugins": ["@babel/plugin-transform-export-namespace-from"] } ``` does *not* solve the problem

While minifying app code: `Unexpected token, expected ":" (1056:150096)`

I am using `3.1`

While minifying app code: `Unexpected token, expected ":" (1056:150096)`

@nachocodoner just take minimal `meteor` repo, add `npm install [email protected]` or `npm install [email protected]` and require (server side) `require('cheerio')`. That should cause the problem.

When meteor2 and meteor3 are in `~/.meteor` then `meteor node` returns the meteor 2 node

... the problem is that `~/.meteor/meteor` to whatever version of meteor was installed first ``` lrwxr-xr-x 1 scharf staff 50 May 14 20:35 meteor -> packages/meteor-tool/2.16.0/mt-os.osx.arm64/meteor ``` I think the...

When meteor2 and meteor3 are in `~/.meteor` then `meteor node` returns the meteor 2 node

Here is a small shim I have written for myself to fix the problem ```bash #!/usr/bin/env bash # Find the original path of the script SCRIPT_DIR=$(dirname "$0") SCRIPT_NAME=$(basename "$0") #...