profile
viewpoint

chriswep/angular-builder-custom-terser-options 0

Angular builder that allows Terser (Uglify) customization

chriswep/angular2-now 0

Code Angular 2 @Component syntax in your Angular 1 apps now

chriswep/angular2-seed-advanced 0

An advanced Angular2 seed project with support for ngrx/store, ng2-translate, angulartics2, lodash, NativeScript (*native* mobile), Electron (Mac, Windows and Linux desktop) and more coming soon...

chriswep/apollo-client 0

:rocket: A simple caching client for any GraphQL server and UI framework

chriswep/capacitor-email 0

Add email support to your Cordova/Ionic/Web projects.

chriswep/CleanStrap 0

CleanStrap: Responsive and Advanced Question2Answer Theme

chriswep/cordova-hot-code-push 0

This plugin provides functionality to perform automatic updates of the web based content in your application.

chriswep/cordova-plugin-dbcopy-capacitor 0

Copy SQLite Database from www folder to default app database location

push eventtyndale/BibleEngine

Chris

commit sha 596c6d19acaf0c8974438bb346f9c3f774a73af0

- throw `BibleBookContentImporting` when book is accessed while it is being imported (thus incomplete) - added `abbreviation` property to BibleVersionEntity (+ migrations)

view details

push time in 5 days

push eventtyndale/BibleEngine

Chris

commit sha bafbc706f609c1d1a3e1683eecde497773479fab

BeDatabaseCreator: make bibleEngine public attribute

view details

push time in 7 days

issue closedionic-team/stencil

Unnecessary polyfills included in Angular differential es2015 build

Stencil version: I'm using Ionic Angular 5.3.3

I'm submitting a: [x] bug? / feature?

Current behavior: When building an Ionic project via Angular, the same exact polyfills files from Stencil are pulled in for both the es5 and es2015 build files:

chunk {5} polyfills-core-js-es2015.79ebeed52926c7a46d5b.js (polyfills-core-js) 91.8 kB  [rendered]
chunk {5} polyfills-core-js-es5.79ebeed52926c7a46d5b.js (polyfills-core-js) 91.8 kB  [rendered]
chunk {6} polyfills-css-shim-es2015.cb3ce672a1e335049b39.js (polyfills-css-shim) 7.91 kB  [rendered]
chunk {6} polyfills-css-shim-es5.cb3ce672a1e335049b39.js (polyfills-css-shim) 7.89 kB  [rendered]
chunk {7} polyfills-dom-es2015.740cf840969ed7443ba5.js (polyfills-dom) 36 kB  [rendered]
chunk {7} polyfills-dom-es5.740cf840969ed7443ba5.js (polyfills-dom) 36 kB  [rendered]

The polyfills from Angular shows the size difference and i suppose that they already contain most of the polyfills included via Stencil (didn't check, i might be wrong):

chunk {4} polyfills-es2015.479c714c8555b532c330.js (polyfills) 36.2 kB [initial] [rendered]
chunk {8} polyfills-es5.e9b04af3da235614344b.js (polyfills-es5) 129 kB [initial] [rendered]

Expected behavior: The es2015 files should be much smaller. There should be no duplicate polyfills generated.

Steps to reproduce: Create a new Ionic project, build.

We are talking about potential 100 kB less build size (or code to parse) for the common es2015 clients (and also for es5 clients if those polyfills are indeed duplicate to the Angular generated ones).

closed time in 7 days

chriswep

issue commentionic-team/stencil

Unnecessary polyfills included in Angular differential es2015 build

Closing, since the generated files are not included in the initial build but only loaded if needed.

chriswep

comment created time in 7 days

issue closedionic-team/stencil

Stencil force including 130KB of prebuilt ES5 polyfills in every build (?)

This is somewhat related to https://github.com/ionic-team/stencil/issues/2682 - a potential fix might solve both issues though. However its still a separate issue that is relevant in contexts outside of the differential build part not working.

Stencil version: I'm using Ionic Angular 5.3.3

I'm submitting a: [x] bug? / feature?

Current behavior: When building an Ionic project via Angular, the following polyfills files from Stencil are included in the build files:

chunk {5} polyfills-core-js.79ebeed52926c7a46d5b.js (polyfills-core-js) 91.8 kB  [rendered]
chunk {6} polyfills-css-shim.cb3ce672a1e335049b39.js (polyfills-css-shim) 7.91 kB  [rendered]
chunk {7} polyfills-dom.740cf840969ed7443ba5.js (polyfills-dom) 36 kB  [rendered]

Angular has its own (dynamic) polyfills mechanism:

chunk {4} polyfills.479c714c8555b532c330.js (polyfills) 36.2 kB [initial] [rendered]

Expected behavior: A lot of the Stencil polyfills are not needed in most contexts. I would also expect that most of the remaining polyfills are already included by existing polyfill mechanisms in builds (like Angular).

Steps to reproduce: Create a new Ionic project, build.

Stencil is pulling in more than 130KB of minified code here that is potentially duplicate or not necessary. This is a huge number in the context of web-apps.

Maybe Ionic should tap into the Angular polyfill mechanism here and not ship prebuilt polyfills. Maybe it could be a solution to add an option to let the user take care of polyfills.

closed time in 8 days

chriswep

issue commentionic-team/stencil

Stencil force including 130KB of prebuilt ES5 polyfills in every build (?)

polyfills are only loaded on runtime if necessary. closing.

chriswep

comment created time in 8 days

push eventtyndale/BibleEngine

Chris

commit sha 8530a54d1faea47c29bf03391235b9088809e15e

- fixed server.syncVersions to accept empty body - fixed core.addBookWithContent to update all book metadata

view details

push time in 11 days

push eventtyndale/BibleEngine

Chris

commit sha 317ea9ead27eb253dc3ea4c939a393e408035794

- added column `type` to BibleVersionEntity and added db-migrations - added `BibleEngine.getVersionLocalId()` - added `syncVersions` method to server API - refactored entity relation notation to prevent circular references - upgrade TypeScript to 4.0.3 - upgrade TypeORM to 0.2.28 - bugfixes

view details

push time in 13 days

issue openedionic-team/stencil

Stencil force including 130KB of prebuilt ES5 polyfills in every build (?)

This is somewhat related to https://github.com/ionic-team/stencil/issues/2682 - a potential fix might solve both issues though. However its still a separate issue that is relevant in contexts outside of the differential build part not working.

Stencil version: I'm using Ionic Angular 5.3.3

I'm submitting a: [x] bug? / feature?

Current behavior: When building an Ionic project via Angular, the following polyfills files from Stencil are included in the build files:

chunk {5} polyfills-core-js.79ebeed52926c7a46d5b.js (polyfills-core-js) 91.8 kB  [rendered]
chunk {6} polyfills-css-shim.cb3ce672a1e335049b39.js (polyfills-css-shim) 7.91 kB  [rendered]
chunk {7} polyfills-dom.740cf840969ed7443ba5.js (polyfills-dom) 36 kB  [rendered]

Angular has its own (dynamic) polyfills mechanism:

chunk {4} polyfills.479c714c8555b532c330.js (polyfills) 36.2 kB [initial] [rendered]

Expected behavior: A lot of the Stencil polyfills are not needed in most contexts. I would also expect that most of the remaining polyfills are already included by existing polyfill mechanisms in builds (like Angular).

Steps to reproduce: Create a new Ionic project, build.

Stencil is pulling in more than 130KB of minified code here that is potentially duplicate or not necessary. This is a huge number in the context of web-apps.

Maybe Ionic should tap into the Angular polyfill mechanism here and not ship prebuilt polyfills. Maybe it could be a solution to add an option to let the user take care of polyfills.

created time in 14 days

issue commenttypeorm/typeorm

0.2.26 brakes browser builds (by node-only PlatformTools refactoring commit)

Sounds like metro isn't recognizing the browser file replacements?

It's either that and/or the fact that the react-native driver uses Platform-Tools to load the driver dependency. E.g. the expo driver does this by passing the dependency on connection.

However if metro would use the browser entry points from package.json it would load BrowserPlatformTools which should also throw an error on .load, but a different one. So the react-native driver needs to be refactored in any case i assume.

chriswep

comment created time in 20 days

issue commentcapacitor-community/sqlite

multiple databases support

if one of the goals is to have a TypeORM driver at the end we could start from there. There is already an abstract sqlite driver in TypeORM that all sqlite-based drivers extend: https://github.com/typeorm/typeorm/tree/master/src/driver/sqlite-abstract. It might make sense to take the Cordova driver as a template for a capacitor driver: https://github.com/typeorm/typeorm/tree/master/src/driver/cordova

For this to work the capacitor plugin needs to have some kind of openDatabase method that returns a connection object with the query method(s) and a close method.

If the latter is done, implementing the typeorm-driver is basically duplicating an existing sqlite driver and making a few minor modifications. As far as i see, TypeORM uses a single query method (which expects query and parameters). The other sqlite pass this to a single driver-method and look if the query starts with INSERT to determine what to return (insertId, array of rows, etc.). In a similar way the capacitor plugin can use its different query methods run/query/execute.

chriswep

comment created time in a month

PR opened TeamHive/capacitor-email

AndroidX compatibility

Updated legacy imports / tags to make this plugin compatible with AndroidX projects

+4 -4

0 comment

2 changed files

pr created time in a month

push eventchriswep/capacitor-email

Chris

commit sha a3fb84ea38687a384c8e1144c602b4a23cacc22f

androidx compatibility in layout

view details

push time in a month

create barnchchriswep/capacitor-email

branch : androidx

created branch time in a month

issue commenttypeorm/typeorm

0.2.26 brakes browser builds (by node-only PlatformTools refactoring commit)

thanks @imnotjames - https://github.com/typeorm/typeorm/pull/6763 seems to do it. no more warnings/errors.

chriswep

comment created time in a month

fork chriswep/capacitor-email

Add email support to your Cordova/Ionic/Web projects.

fork in a month

issue commentcapacitor-community/sqlite

ORM support

i think using typeorm would make the most sense here. there are also similar plugins for cordova-sqlite and others that can be taken as a start.

Together with multiple database support (https://github.com/capacitor-community/sqlite/issues/1) this would make this plugin useful in many more use cases.

pritamsoni-hsr

comment created time in a month

issue commentcapacitor-community/sqlite

multiple databases support

@jepiqueau seeing this now is the kind of "official" sqlite community capacitor plugin i want to reopen this discussion to avoid potentially creating a second plugin for mostly the same purpose. i'm currently still using the Cordova plugin in capacitor however i want to get rid of it at some time.

I looked into the code a bit and it seems to me that this plugin indeed creates a new connection for each request/query/transaction. Can someone shed some light on the performance overhead for this? And apart from performance this also doesn't seem to be how a database (and also the underlying sqlite implementations) are supposed to work?

If we want to use multiple databases there comes the issue of parallelism into play. If i see it correctly the plugin currently saves the database name and options in its internal state. So we would need to use open and close before and after each call to execute on this plugin. And if i don't overlook something this still wouldn't make 100% sure that parallel queries go to the correct database (or break another running operation) since they all operate on the same global CapacitorSQLPlugin object and its state.

I suggest to refactor this to return some kind of db-handle object when opening a database. I suppose this would involve separating some methods into a new class that handles the connection/db-handle in its state. Opening a database would then return an instance to this class. This way apps could have multiple database handles open that can be safely used in parallel. Also the plugin wouldn't need to open and close the database for each query/transaction.

For backwards compatibility, an instance of this db-handle class could be used internally by the plugin on default and only returned requested specifically.

chriswep

comment created time in a month

IssuesEvent

issue commenttypeorm/typeorm

0.2.26 brakes browser builds (by node-only PlatformTools refactoring commit)

i also see the warnings in the testing repository. i created simple connection via createConnection({ type: "sqlite", name: "memory", database: ":memory:" }); in main.ts - so maybe you have to do something like that so that something significant gets actually bundled by webpack.

i managed to make it build by telling webpack to include a polyfill for node-path. however my build now a few hundred kB bigger, including full versions of xmlbuilder, js-yaml, sax, esprima ... i think this is related to the webpack warning Critical dependency: the request of a dependency is an expression - it looks like it has to pull in everything if a dep is required in an expression like that. It makes sense to me that this should be avoided (see https://github.com/webpack/webpack/issues/196#issuecomment-71917456).

Concerning the option: I actually started the approach with the browser entry in package.json. Its a hack though. And it breaks every second typeorm release (hello again). i would think that fixing/refactoring the dependency-as-expression thing would solve the immediate issue here wouldn't it? ConnectionOptionsReader can't really be replace by a dummy i suppose, ConnectionOptionsXmlReader might be but this could also be used in a browser build.

I think the proper way forward would be to separate core and drivers / plugins. A new driver shouldn't have to update (or even affect) various core files.

chriswep

comment created time in a month

issue commenttypeorm/typeorm

0.2.26 brakes browser builds (by node-only PlatformTools refactoring commit)

@imnotjames some of the issues still remain:

WARNING in /Volumes/Users/chris/code/forks/typeorm/build/package/browser/connection/ConnectionOptionsReader.js 113:45-64
Critical dependency: the request of a dependency is an expression

WARNING in /Volumes/Users/chris/code/forks/typeorm/build/package/browser/connection/ConnectionOptionsReader.js 119:45-64
Critical dependency: the request of a dependency is an expression

WARNING in /Volumes/Users/chris/code/forks/typeorm/build/package/browser/connection/ConnectionOptionsReader.js 125:44-63
Critical dependency: the request of a dependency is an expression

WARNING in ../node_modules/typeorm/node_modules/sax/lib/sax.js
Module not found: Error: Can't resolve 'stream' in '/Volumes/Users/chris/code/emmaus/emmono/node_modules/typeorm/node_modules/sax/lib'

And the following errors:

ERROR in ../node_modules/typeorm/node_modules/app-root-path/browser-shim.js
Module not found: Error: Can't resolve 'path' in '/Volumes/Users/chris/code/emmaus/emmono/node_modules/typeorm/node_modules/app-root-path'

ERROR in ../node_modules/typeorm/node_modules/xml2js/lib/parser.js
Module not found: Error: Can't resolve 'timers' in '/Volumes/Users/chris/code/emmaus/emmono/node_modules/typeorm/node_modules/xml2js/lib'

Those still hint to node-stuff being loaded. All those messages are related to the PlatformTools refactoring.

chriswep

comment created time in a month

issue openedionic-team/stencil

Unnecessary polyfills included in Angular differential build

Stencil version: I'm using Ionic Angular 5.3.3

I'm submitting a: [x] bug? / feature?

Current behavior: When building an Ionic project via Angular, the same exact polyfills files from Stencil are pulled in for both the es5 and es2015 build files:

chunk {5} polyfills-core-js-es2015.79ebeed52926c7a46d5b.js (polyfills-core-js) 91.8 kB  [rendered]
chunk {5} polyfills-core-js-es5.79ebeed52926c7a46d5b.js (polyfills-core-js) 91.8 kB  [rendered]
chunk {6} polyfills-css-shim-es2015.cb3ce672a1e335049b39.js (polyfills-css-shim) 7.91 kB  [rendered]
chunk {6} polyfills-css-shim-es5.cb3ce672a1e335049b39.js (polyfills-css-shim) 7.89 kB  [rendered]
chunk {7} polyfills-dom-es2015.740cf840969ed7443ba5.js (polyfills-dom) 36 kB  [rendered]
chunk {7} polyfills-dom-es5.740cf840969ed7443ba5.js (polyfills-dom) 36 kB  [rendered]

The polyfills from Angular shows the size difference and i suppose that they already contain most of the polyfills included via Stencil (didn't check, i might be wrong):

chunk {4} polyfills-es2015.479c714c8555b532c330.js (polyfills) 36.2 kB [initial] [rendered]
chunk {8} polyfills-es5.e9b04af3da235614344b.js (polyfills-es5) 129 kB [initial] [rendered]

Expected behavior: The es2015 files should be much smaller. There should be no duplicate polyfills generated.

Steps to reproduce: Create a new Ionic project, build.

We are talking about potential 100 kB less build size (or code to parse) for the common es2015 clients (and also for es5 clients if those polyfills are indeed duplicate to the Angular generated ones).

created time in a month

issue openedionic-team/stencil

bug: polyfill for Event.composedPath returning wrong type, breaking other ionic code when active

Bug Report

Ionic version: [x] 5.3.3

Current behavior: The polyfill for Event.composedPath in @ionic/core/dist/esm/polyfills/dom.js returns a NodeList, however it should return an Array (https://developer.mozilla.org/en-US/docs/Web/API/Event/composedPath). NodeList does not support array methods like include(), which breaks code using the output of composedPath() like that. For example this affects https://github.com/ionic-team/ionic-framework/blob/master/core/src/components/tab-button/tab-button.tsx#L85, which triggers an error when run on clients that load the polyfill.

Since i stumbled upon this: i suppose https://github.com/ionic-team/ionic-framework/issues/20038 is caused by the same issue.

Expected behavior: Event.composedPath polyfill should return an array.

created time in a month

issue openedionic-team/ionic-framework

bug: polyfill for Event.composedPath returning wrong type, breaking other ionic code when active

Bug Report

Ionic version: [x] 5.3.3

Current behavior: The polyfill for Event.composedPath in @ionic/core/dist/esm/polyfills/dom.js returns a NodeList, however it should return an Array (https://developer.mozilla.org/en-US/docs/Web/API/Event/composedPath). NodeList does not support array methods like include(), which breaks code using the output of composedPath() like that. For example this affects https://github.com/ionic-team/ionic-framework/blob/master/core/src/components/tab-button/tab-button.tsx#L85, which triggers an error when run on clients that load the polyfill.

Since i stumbled upon this: i suppose https://github.com/ionic-team/ionic-framework/issues/20038 is caused by the same issue.

Expected behavior: Event.composedPath polyfill should return an array.

created time in a month

issue commenttypeorm/typeorm

0.2.26 brakes browser builds (by node-only PlatformTools refactoring commit)

Thanks @imnotjames, that looks helpful. However I am using SQLite in a browser context in a Hybrid App (via Cordova/capacitor, most electron apps would be affected as well I guess). Can a similar more finegrained approach be used that doesn't exclude the whole driver?

chriswep

comment created time in a month

issue commenttypeorm/typeorm

0.2.26 brakes browser builds (by node-only PlatformTools refactoring commit)

ok, i just made a quick test via https://github.com/juristr/webpack-typescript-starter, imported typeorm in main.ts and did npm run build. It shows (most of) the same errors. So it seems to be unrelated to both Angular and my project setup but rather affect browser targets in general @pleerock @imnotjames ?

chriswep

comment created time in a month

issue commenttypeorm/typeorm

0.2.26 brakes browser builds (by node-only PlatformTools refactoring commit)

@pleerock i get your point, however i'm not sure i agree that breaking existing projects in a patch release is the best path to a solution.

At this point i'm also not sure if this is really related to Angular but rather to browser targets in general. @imnotjames did you successfully use this for a webpack build with a browser target? It pulls in several node-only dependencies, so i would expect this to only build and run successfully for node targets.

chriswep

comment created time in a month

issue commenttypeorm/typeorm

0.2.26 brakes browser builds (by node-only PlatformTools refactoring commit)

@imnotjames i'm using angular which generates a config via its devkit. i guess this is where it pulls the configs from: https://github.com/angular/angular-cli/tree/master/packages/angular_devkit/build_angular/src/webpack/configs

i would expect the issue to show up if you create a simple angular project (with typeorm imported at some place in the code) and ng build it. I'm using TypeScript 4.

maybe i'm missing something here, but seeing that the compiler has a code path to require('fs') (using the browser entry point), it makes sense to me that it fails.

i can see that typeorms way of handling both node and browser needs refactoring (i had a fair bit of working around issues here as well). however it looks like this needs a more thorough approach? thats why i suggested to revert the attempt until there is a working solution - unless there is an easy fix for this of course.

chriswep

comment created time in a month

issue openedtypeorm/typeorm

0.2.26 brakes browser builds (by node-only PlatformTools refactoring commit)

Issue type: [x] bug report

Database system/driver: all / doesn't build

TypeORM version: [x] 0.2.26

Steps to reproduce or a small repository showing the problem: Building a project with TypeORM 0.2.26 with webpack for a browser target leads to multiple errors, the following is just just an excerpt (with duplicates removed):

WARNING in ../node_modules/typeorm/browser/connection/ConnectionOptionsReader.js 114:45-64
Critical dependency: the request of a dependency is an expression

WARNING in ../node_modules/typeorm/browser/util/DirectoryExportedClassesLoader.js 38:38-78
Critical dependency: the request of a dependency is an expression

Module not found: Error: Can't resolve 'path'

Module not found: Error: Can't resolve 'stream'

Module not found: Error: Can't resolve 'fs'

Module not found: Error: Can't resolve 'timers'

I could track this down to this commit: https://github.com/typeorm/typeorm/commit/490ad0d424e674de5be38b0c3bc83b9a14a383a5

I reverted this commit locally and could then successfully use 0.2.26 with this modification in a browser Webpack build.

I guess that https://github.com/typeorm/typeorm/pull/6630 didn't take browser builds into account for its refactoring. On a quick look those errors (and the code changes in the pull request) do look like node-only stuff.

I suggest reverting the commit/PR @pleerock.

created time in a month

push eventchriswep/typeorm

Chris

commit sha 650b71665bdf197b1b216f39456cf8aeef4149ed

closes #6110 (#6117) added `AuroraDataApiPostgresDriver` to `BrowserDisabledDriversDummy.template` to fix typeorm not compiling when using browser target

view details

Sergio Durban Belmonte

commit sha 203f51d08ed3ec4d4a1004dc730d09e1cd03f142

feat: add AWS configurationOptions to aurora-data-api-pg connector (#6106) Co-authored-by: Sergio Durban Belmonte <sdurban@leadtech.com>

view details

Mike MacCana

commit sha b4a29f4b383b3d9dbc6b1d3bfa48f8d77bec36c4

docs: add a link to TypeORM website (#6143) Weirdly search sent me here, and it took a while to find the real TypeORM website.

view details

Umed Khudoiberdiev

commit sha e073e027808f388f12cf374a6a305c25222bf242

fix: revert fix handle URL objects as column field values (#6145) This reverts commit 50a0641592c21f32a89c1be38da75ca6e7ac0f5a.

view details

Umed Khudoiberdiev

commit sha a595fedc2e159e2eb0c4c5d76bff31ac98da3df2

fix: SqlQueryRunner.hasColumn was not working (#6146) * fixed #5718 * removed .only

view details

Jack Wink

commit sha 007214986e421621eb4ec858907e51ae083c1cf7

feat: add postgres connection timeout option (#6160) There was no documented way of setting a connection timeout for the postgres driver. We recently ran into an issue with our network that caused a container to hang indefinitely attempting to connect to postgres. We managed to resolve the issue by setting 'connectionTimeoutMillis' in the 'extra' field of our connection options. This approach does not appear to be documented anywhere. Seeing that MongoDB and MySQL drivers both support a connection timeout as part of the documented API, we felt it made sense to add a similar option to the Postgres driver and hopefully avoid some headaches down the road. This commit adds a 'connectTimeoutMS' option to the postgres driver that gets translated to the appropriate field for the pg library. It also updates the documentation to reflect this new option. Because the default behavior of the underlying pg library is to attempt to connect indefinitely, we didn't feel like it was a safe change to introduce a default timeout, even if that's more sane behavior. As mentioned earlier, both the MySQL and MongoDB drivers support a connection timeout option. MySQL uses 'connectTimeout' while MongoDB uses 'connectTimeoutMS'. We went with 'connectTimeoutMS' as to not introduce yet another name for a connection timeout, and because the 'MS' suffix makes it clearer what is expected. We hope a future PR may adjust the MySQL connection options to adopt the same name, but will leave that up to someone with a stronger opinion.

view details

Giancarlos Isasi

commit sha defa9bced0b5d1258e4f50d5c590978e6d3324d3

docs: fix undefined `repository` variable on docs (#6221) The `repository` variable is not defined in the first Data Mapper pattern example

view details

Umed Khudoiberdiev

commit sha fc7a4f13f6270c9d5206358ebd78adb0ca690b3d

added sap hana note

view details

0xflotus

commit sha 9a887518f58f6a5917f39ee5db19351e067686e6

docs: fixed small error (#6258)

view details

Mustapha Yusuff

commit sha 1c09dc31f3e4d64657bf711228741ae7b10f4088

docs: replace body-parser with express built-in parser (#6257) JSON body parser is now built-in by default (>4.16.0), hence no need for body-parser

view details

Nipodemos

commit sha 4073a8dafaeebeb559b1e260e75761eb40150204

docs: fix markdown typo (#6359)

view details

Rahul Soni

commit sha 1bc56588be598e9a17fb9ddf870311809a034bdc

docs: update relations-faq.md (#6355) Grammatical error

view details

Pedro Silveira Lopes

commit sha 8e2d97dd1fa036bd83479c457e58d9ea49c8f151

fix: resolve missing decorators on shim (#6354) Closes: #6093

view details

IAGO BRAYHAM

commit sha 60711c292422cb3b9cf3843613d4cb3977a8f124

docs: Add advance subdocument query documentation (#6344) Example for querying subdocuments and array of subdocuments

view details

yokomotod

commit sha 0d99b4662518c8489e9aeba9d87a8028e16c3899

fix: remove unnecessary optionality from Raw operator's columnAlias argument (#6321)

view details

Angel J Piscola

commit sha 0ba2a48efdf18977ff5df55b950e763255c75ffc

fix: properly override database url properties (#6247) * fix: properly override database url properties Closes #4878 * test: add test for overriding url options

view details

Dan Pickett

commit sha 6eeb03aa95018e37b0bd09f72296b1fdc17cbbd3

feat: support cjs extension for ormconfig (#6285) * support cjs extension for ormconfig * fix linting errors * handle cjs extensions in class loader

view details

Ryan

commit sha 6f6bdbd2b760ab3ca56013c4789ddc8f72c63dc6

fix: insert IN(null) instead of IN() when In([]) empty array for mysqlDriver (#6237) fix: lint warning Co-authored-by: shitong.zheng <shitong.zheng@shopee.com>

view details

dependabot[bot]

commit sha 51af310b2104fe1f2dd619f63fdda9699bdd47a2

chore(deps): bump lodash from 4.17.15 to 4.17.19 (#6408) Bumps [lodash](https://github.com/lodash/lodash) from 4.17.15 to 4.17.19. - [Release notes](https://github.com/lodash/lodash/releases) - [Commits](https://github.com/lodash/lodash/compare/4.17.15...4.17.19) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

view details

Fernando Moreira

commit sha c9f184e887baa87d92790a91e495c6d2e52ff12f

docs: update using-cli.md (#6407)

view details

push time in a month

issue commentionic-team/ionic-framework

bug: getTab is not accessible

@liamdebeasi is there any way to get an instance of IonTab? i couldn't find a way. If i read the code directly ionic-angular doesn't even use the ion-tab element. However it has a dedicated page in the documentation.

My use case is resetting tabs to their root/inital components/pages on logout.

znotdead

comment created time in a month

push eventchriswep/angular-builders

Chris

commit sha bfa2be285538ce4b7f86a32489c3aafda7d601e4

Update package.json

view details

push time in 2 months

push eventchriswep/angular-builders

Chris

commit sha 14d3713c5c751b9527e8a1d4e5d125edc448c10b

Update package.json

view details

push time in 2 months

push eventchriswep/angular-devkit-build-angular-builds

Chris

commit sha 49b1c4a2a510adc8dcdb2aace4f4db7f8ad071c3

Revert "Update process-bundle.js"

view details

Chris

commit sha 4c8f38b48d41cd76fd87b64ba52e50d688b7a5dd

Merge pull request #2 from chriswep/revert-1-chriswep-patch-terserOptions Revert "Update process-bundle.js"

view details

push time in 2 months

push eventchriswep/angular-devkit-build-angular-builds

Chris

commit sha 3f9cc38463768687c0e642e0dd055b1e37385acd

Update process-bundle.js

view details

Chris

commit sha 08bd4d867174b343fb6b819f7a91dbb83f542322

Merge pull request #1 from chriswep/chriswep-patch-terserOptions Update process-bundle.js

view details

push time in 2 months

push eventchriswep/angular-builders

Chris

commit sha 6a3d9560904eabc7ff8d28e7209edc67a9c76da1

Update package.json

view details

push time in 2 months

push eventchriswep/angular-devkit-build-angular-builds

Chris

commit sha d5c4c4197c84f2e6c8333f050ac9e69878431260

Update process-bundle.js added regex for terserOptions.keep_fnames

view details

push time in 2 months

push eventchriswep/angular-builders

Chris

commit sha 8cfeba6209dbdd34f86fef224abdae657048e341

Update package.json

view details

push time in 2 months

fork chriswep/angular-builders

Angular build facade extensions (Jest and custom webpack configuration)

fork in 2 months

push eventtyndale/BibleEngine

Chris

commit sha 0821a41f993e8aef4eab44ac7246276421c8ca4b

added more information to an error message in v11n normalization

view details

push time in 2 months

issue commenttypeorm/typeorm

Typeorm/browser cannot be compiled since version 0.2.25

I am still getting this error:

I am on the latest version (yarn add typeorm@latest => "typeorm": "^0.2.25").

That's still the version with the error. Unfortunately typeorm hasn't released a new version yet.

clfhhc

comment created time in 3 months

more