manks
January 1, 2022, 9:27pm
1
I’m in need of adding a date-time picker to my app, and I’m wondering which ones you use. I’m currently using Bootstrap 5 + Aurelia 1.
Flatpickr seems to be a dead project, and the Aurelia npm package aurelia-flatpickr is 6 years old!
Tempus Dominus is in version 6-alpha, but seems like it’s under active development . There is no Aurelia npm package for it, but that’s ok.
npm package aurelia-bootstrap-datetimepicker is no longer current, and it’s GitHub repo was actually removed, and it’s replacement aurelia-bootstrap-plugins hasn’t been updated in 3 years . I’m not even sure they would work with Bootstrap 5, anyway.
The native HTML5 date input seems limited.
Thoughts?
2 Likes
We were in the same situation some weeks ago. As we did not find a date picker that meets our requirements and is still under active development, we decided to build one ourselves.
With the support of DayJs as our date library, it’s not that complex!
If you are interested, I would share the code.
(culture in screenshot: german, additional cultures supported)
3 Likes
manks
January 4, 2022, 3:42pm
3
Awesome! Have you considered open sourcing it? Maybe create a GitHub/npm account for Aurelia components?
i’ve used https://litepicker.com/ for one of my projects and am pretty happy with it
this.createdAtPicker = new Litepicker({
element: this.txtCreatedAt,
numberOfMonths: 2,
numberOfColumns: 2,
singleMode: false,
delimiter: " .. ",
useResetBtn: true,
onHide: () => {
this.txtCreatedAt.dispatchEvent(new CustomEvent("change"));
}
});
the example shows one additional bit where I trigger the change event when hiding the picker so that aurelia picks up the change
2 Likes
I’ve been using LitePicker too
1 Like
To offer this as “ready to use” open source library, it would need further work in terms of flexibility, configurability, styling, build pipeline, etc.
As it’s little, simple and clean code, I could share the code and you could use it directly in your codebase with customisations according to your needs.
manks
January 6, 2022, 4:20pm
8
Sure, that would be great!
manks
January 6, 2022, 4:25pm
9
LitePicker looks, good. And I could always just write my own time selector. By the way, have you guys noticed the calendar tool for comment entry?
nope, I’ve merely used it in dual mode for selecting a day range. but looks interesting
For all of my projects I’ve been using FlatPickr. When used on mobile, it’ll use the native time/date pickers instead. You can force it to just stick to the web version though. Lightweight and no other dependencies.
1 Like
manks
January 7, 2022, 12:26am
12
I looked at Flatpickr but it seems to be a dead project. Am I wrong?
I’ve just had a look at the issues/commits and it still seems very alive, with donations streaming in for the maintainer too.
manks
January 10, 2022, 4:53pm
15
@MaximBalaganskiy Is that your repo? Nice collection. I was thinking of doing the same for the Toast-UI components. Maybe I can contribute to your repo if you want to extend it’s offerings/functionality.
zewa666
January 10, 2022, 5:08pm
16
what did you end up choosing?
@manks sure, why not… this set is basically shared code for all my projects across several orgs except mdc components , which live separately
manks
January 16, 2022, 1:24am
18
I got hit with two bugs today that set me back a day. I guess next weekend I can start on playing with the toast-ui editor and calendar. Nothing is ever smooth.
opened 06:33PM - 19 Oct 21 UTC
closed 08:58PM - 28 Oct 21 UTC
webpack-4
webpack-5
critical-bug
# Bug report
**What is the current behavior?**
```sh
[webpack-c… li] Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:67:19)
at Object.createHash (node:crypto:130:10)
at BulkUpdateDecorator.hashFactory (/opt/src/node_modules/webpack/lib/util/createHash.js:155:18)
at BulkUpdateDecorator.digest (/opt/src/node_modules/webpack/lib/util/createHash.js:80:21)
at /opt/src/node_modules/webpack/lib/DefinePlugin.js:595:38
at Hook.eval [as call] (eval at create (/opt/src/node_modules/tapable/lib/HookCodeFactory.js:19:10), <anonymous>:100:1)
at Hook.CALL_DELEGATE [as _call] (/opt/src/node_modules/tapable/lib/Hook.js:14:14)
at Compiler.newCompilation (/opt/src/node_modules/webpack/lib/Compiler.js:1053:26)
at /opt/src/node_modules/webpack/lib/Compiler.js:1097:29
at Hook.eval [as callAsync] (eval at create (/opt/src/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1) {
opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
library: 'digital envelope routines',
reason: 'unsupported',
code: 'ERR_OSSL_EVP_UNSUPPORTED'
}
```
**Other relevant information:**
webpack version: 5.59.0
Node.js version: 17.0.0
Operating System: linux x64
opened 09:36AM - 10 Sep 21 UTC
closed 11:42PM - 08 Dec 21 UTC
Needs Investigation
# Bug Report
### 🔎 Search Terms
SyntaxError: Named export not found. The r… equested module is a CommonJS module, which may not support all module.exports as named exports, esm, exports, __exportStar, tslib
### 🕗 Version & Regression Information
- This changed between versions 4.4 and 4.3
### ⏯ Playground Link
Playground links demonstrate the difference in compiled output between versions
[Playground link with relevant code (4.4)](https://www.typescriptlang.org/play?importHelpers=true&module=1&ts=4.4.2#code/KYDwDg9gTgLgBAKjgMyhAtnA5MgzlgbiA)
[Playground link with relevant code (4.3)](https://www.typescriptlang.org/play?importHelpers=true&module=1&ts=4.3.5#code/KYDwDg9gTgLgBAKjgMyhAtnA5MgzlgbiA)
[Full reproduction repo and instructions](https://github.com/maxholman/ts-4.4-exports)
### 💻 Code
From the above Playground link, 4.4 produces:
```js
"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
const tslib_1 = require("tslib");
(0, tslib_1.__exportStar)(require("fs"), exports);
```
4.3 produces:
```js
"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
const tslib_1 = require("tslib");
tslib_1.__exportStar(require("fs"), exports);
```
Note the use of the comma operator to unbind `__exportStar`. This seems to be new in 4.4 via [more indirect calls for imported functions](https://devblogs.microsoft.com/typescript/announcing-typescript-4-4/#more-compliant-indirect-calls-for-imported-functions) and https://github.com/microsoft/TypeScript/pull/44624
### 🙁 Actual behavior
Named exports are missing when importing a CommonJS module compiled with Typescript 4.4 when `importHelpers` is `true`.
Setting `importHelpers` to false fixes this problem, but may result in a lot of duplicated code via `tslib`
### 🙂 Expected behavior
Named exports should either exist, whether I have `importHelpers` turned on or off.... or would be good this this was specifically documented as a breaking change.
(possibly) related: https://github.com/microsoft/TypeScript/issues/45189
opened 04:49PM - 13 Oct 21 UTC
Hi, I'm hoping this is the right place to post this! I just learned about this p… roject when investigating an issue with named imports in NestJS.
TypeScript made a [change](https://github.com/microsoft/TypeScript/pull/44624) to how certain function calls are compiled to CommonJS in version 4.4. Long story short, when you write `export * from "./foo";` in TypeScript, in 4.3 and earlier it would write something like:
tslib_1.__exportStar(require("./foo"), exports);
But in 4.4 it's writing:
(0, tslib_1.__exportStar)(require("./foo"), exports);
I ran into this while investigating [an issue I ran into](https://github.com/nestjs/nest/issues/8320) when upgrading NestJS, and [it seems others are experiencing the same problems with other packages](https://github.com/microsoft/TypeScript/issues/45813).
Like I said, I'm not very familiar with this project, but is it possible that the parsing code could be updated to handle this new syntax? I expect this is going to affect more and more CommonJS projects written in TypeScript as they release new versions compiled with 4.4 or later.