profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/evenfrost/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Aleksey Kislov evenfrost Pythia AI Tallinn, Estonia https://pythia.cc CTO @ Pythia | AI solutions for Zendesk

evenfrost/bulker 5

Perform bulk manipulations with DOM elements

evenfrost/booted 2

My pretty opinionated JS boilerplate

evenfrost/esnext 1

A boilerplate for writing ES.next apps

evenfrost/framescroller 1

A JavaScript module to create a scrolling video from image frames.

evenfrost/angular-dragula 0

:ok_hand: Drag and drop so simple it hurts

evenfrost/ansible-role-nodejs 0

Ansible Role - Node.js.

evenfrost/astro 0

🚀🧑‍🚀 Keep your eyes to the skies, astronauts!

evenfrost/babel-plugin-react-css-modules 0

Transforms styleName to className using compile time CSS module resolution.

evenfrost/babel.github.io 0

:globe_with_meridians: The Babel documentation website

startedRensAlthuis/vertical-overview

started time in 7 days

startedremarkablemark/html-react-parser

started time in 14 days

PR closed snowpackjs/astro

Update Tailwind docs

Changes

Updated the Tailwind docs to match new rules coming from the 0.20 Astro release (public folder is no more being built).

Testing

<!-- How was this change tested? --> <!-- DON'T DELETE THIS SECTION! If no tests added, explain why. --> Docs update, no testing done.

Docs

<!-- Was public documentation updated? --> <!-- DON'T DELETE THIS SECTION! If no docs added, explain why (e.g. "bug fix only") --> This is an docs update itself.

+8 -0

4 comments

1 changed file

evenfrost

pr closed time in 17 days

pull request commentsnowpackjs/astro

Update Tailwind docs

Thanks all, I think it can be closed in favor of https://github.com/snowpackjs/astro/pull/1262.

evenfrost

comment created time in 17 days

Pull request review commentsnowpackjs/astro

Update Tailwind docs

 Now you're ready to write Tailwind! Our recommended approach is to create a `src @tailwind utilities; ``` +and then import the file to a layout you want to use Tailwind in:

@FredKSchott true, as was mentioned by @drwpow above.

evenfrost

comment created time in 17 days

PullRequestReviewEvent

pull request commentsnowpackjs/astro

stop building, bundling, and transforming public/ files

@matthewp I've opened a PR about it with the changes to the docs concerning the public folder but saw too late you've done it before me 😅 . Feel free to close this PR, but I believe that this line about importing the global.css is still important as it won't be automatically imported in Astro templates, am I right?

FredKSchott

comment created time in 18 days

PR opened snowpackjs/astro

Update Tailwind docs

Changes

Updated the Tailwind docs to match new rules coming from the 0.20 Astro release (public folder is no more being built).

Testing

<!-- How was this change tested? --> <!-- DON'T DELETE THIS SECTION! If no tests added, explain why. --> Docs update, no testing done.

Docs

<!-- Was public documentation updated? --> <!-- DON'T DELETE THIS SECTION! If no docs added, explain why (e.g. "bug fix only") --> This is an docs update itself.

+8 -0

0 comment

1 changed file

pr created time in 18 days

create barnchevenfrost/astro

branch : tailwind-docs-fix

created branch time in 18 days

fork evenfrost/astro

🚀🧑‍🚀 Keep your eyes to the skies, astronauts!

https://astro.build

fork in 18 days

pull request commentsnowpackjs/astro

stop building, bundling, and transforming public/ files

@matthewp no need to make an issue I guess, it's enough to put @tailwind utilities in e.g. /styles/index.css and import them into a layout where you need them via

import '../styles/index.css';

Though a slightly more handful approach would be not to import such global CSS into every layout and make them available globally somehow, it would be overkill to implement such logic for now for such small tradeoff.

FredKSchott

comment created time in 18 days

startedz0ccc/Vytal

started time in 18 days

pull request commentsnowpackjs/astro

stop building, bundling, and transforming public/ files

@matthewp is there a recommended approach to put styles that 1. need to be built and 2. need to be available globally, e.g. for all Astro components and pages? I tried to put the Tailwind init styles to src/styles/index.css but that unsurprisingly didn't work.

FredKSchott

comment created time in 21 days

pull request commentsnowpackjs/astro

stop building, bundling, and transforming public/ files

@FredKSchott how the Tailwind config should be implemented now? Tailwind styling documentation notes:

Our recommended approach is to create a public/global.css file (or whatever you‘d like to name your global stylesheet) with Tailwind utilities like so:

/* public/global.css */
@tailwind base;
@tailwind components;
@tailwind utilities;

But that won't work now as the public folder is no more being transformed.

FredKSchott

comment created time in 22 days

startedmicrosoft/fast

started time in a month

issue commentapollographql/apollo-client

MutationTuple now requires 4 arguments instead of 2

Looks good now, thanks.

evenfrost

comment created time in a month

startedelbywan/wretch-middlewares

started time in a month

issue commenttailwindlabs/tailwindcss

Enabling JIT breaks sourcemaps in webpack + PostCSS project

@adamwathan FYI, sourcemaps still not working with JIT enabled in 2.2.7. Screenshot from 2021-08-04 11-53-26 Screenshot from 2021-08-04 11-55-11

evenfrost

comment created time in a month

issue openedapollographql/apollo-client

MutationTuple now requires 4 arguments instead of 2

After upgrading to @apollo/client from v3.3.x to v3.4.1 our codebase broke as MutationTuple interface now requires 4 type arguments instead of 2. MutationTuple is used to explicitly type our mutation functions.

Is there a reason these arguments are not made optional? I'd consider it a breaking change then, because it, literally, breaks the code.

created time in a month

startedmyspaghetti/macos-virtualbox

started time in 2 months

issue commentValveSoftware/Proton

The Elder Scrolls Online (306130)

@kaydenl yeah, I removed PROTON_NO_ESYNC=1 some time ago as it was causing very frequent crashes in some areas. From that time, I face some occasional crashes, but they're not hourly, more like once in 2-3 hours of playing, and are completely random, not caused by a specific action or a hardware issue (like laptop overheating or too much RAM used). My ulimit is 1048576, which is more than 500 000.

diraven

comment created time in 2 months

issue openedtailwindlabs/tailwindcss

Enabling JIT breaks sourcemaps in webpack + PostCSS project

What version of Tailwind CSS are you using?

2.2.6

What build tool (or framework if it abstracts the build tool) are you using?

webpack 5.46.0, postcss 8.3.6

What version of Node.js are you using?

14.17.0

What browser are you using?

Chrome

What operating system are you using?

Ubuntu

Reproduction repository

Describe your issue

When using Tailwind's JIT option for processing PostCSS in the webpack project, source maps are not being shown in the Chrome DevTools (but still generated in the output CSS file). The value of devtool option in the webpack config doesn't matter, the result is the same.

With config like this:

  purge: [
    './src/**/*.tsx',
  ],
  mode: 'jit',

Source maps don't get processed: Screenshot from 2021-07-22 16-36-57

When disabling the JIT option:

  purge: false,

Source maps are being processed properly, and the original file is shown in Chrome DevTools: Screenshot from 2021-07-22 16-30-51

I'll bootstrap a repro repo if a more thorough investigation is needed.

created time in 2 months

issue commenttailwindlabs/tailwindcss

mode: 'jit' - "@apply is not supported within nested at-rules like @screen"

@adamwathan This happens as well with PostCSS nesting enabled (nesting-rules: true in postcss-preset-env config) when jit is enabled in Tailwind config. When jit is disabled, everything processes correctly, and the error is not thrown.

Florian-crg

comment created time in 2 months

startedalexmacarthur/probaclick

started time in 2 months

issue commentValveSoftware/Proton

The Elder Scrolls Online (306130)

If someone got a fix for random infrequent crashes of the game, that would be very helpful. Tried to run the game with different Proton versions (including GE), graphical settings, environmental params with no luck. The game crashes once in a few hours, either just freezes or some obscure Wine error popup appears.

diraven

comment created time in 2 months

issue openedmikro-orm/mikro-orm

Specifiing explicit type on array column in Postgres results in 'malformed array literal' error

Describe the bug In PostgreSQL, when you define columns with explicit columnType, insert operations generate invalid syntax (["value"] instead of {value}), which results in malformed array literal: "["value"]" error. If column type is not specified and the type inherited from TS, insert queries are generated properly.

Stack trace

(node:479180) UnhandledPromiseRejectionWarning: DriverException: insert into "dashboardHealthCheckItems" ("category", "createdAt", "details", "id", "impact", "label", "prerequisites", "product", "solution", "title", "type", "updatedAt", "valueDescription", "valueLabels") values ('branding', '2021-07-15T08:47:36.511Z', '', 'd86b569f-0c28-4baa-b27a-2c91e8a165fe', 'low', 'missing-avatars', '["foo"]', 'zendesk-support', '', '', 'suggestion', '2021-07-15T08:47:36.512Z', '', '["customer-friendliness","account-branding"]') returning "id" - malformed array literal: "["foo"]"
at PostgreSqlExceptionConverter.convertException (/home/evenfrost/work/projects/pythia/source/pythia-core/node_modules/@mikro-orm/core/platforms/ExceptionConverter.js:8:16)
at PostgreSqlExceptionConverter.convertException (/home/evenfrost/work/projects/pythia/source/pythia-core/node_modules/@mikro-orm/postgresql/PostgreSqlExceptionConverter.js:40:22)
at PostgreSqlDriver.convertException (/home/evenfrost/work/projects/pythia/source/pythia-core/node_modules/@mikro-orm/core/drivers/DatabaseDriver.js:194:54)
at /home/evenfrost/work/projects/pythia/source/pythia-core/node_modules/@mikro-orm/core/drivers/DatabaseDriver.js:198:24
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at PostgreSqlDriver.nativeInsert (/home/evenfrost/work/projects/pythia/source/pythia-core/node_modules/@mikro-orm/knex/AbstractSqlDriver.js:154:21)
at ChangeSetPersister.persistNewEntity (/home/evenfrost/work/projects/pythia/source/pythia-core/node_modules/@mikro-orm/core/unit-of-work/ChangeSetPersister.js:55:21)
at ChangeSetPersister.executeInserts (/home/evenfrost/work/projects/pythia/source/pythia-core/node_modules/@mikro-orm/core/unit-of-work/ChangeSetPersister.js:24:13)
at UnitOfWork.commitCreateChangeSets (/home/evenfrost/work/projects/pythia/source/pythia-core/node_modules/@mikro-orm/core/unit-of-work/UnitOfWork.js:501:9)
at UnitOfWork.persistToDatabase (/home/evenfrost/work/projects/pythia/source/pythia-core/node_modules/@mikro-orm/core/unit-of-work/UnitOfWork.js:458:13)


...

To Reproduce Steps to reproduce the behavior:

  1. Define your entity with array column and explicit columnType (type: ArrayType causes the error too).
  @Property({ columnType: 'text[]' })
  tags: string[];
  1. Run a simple insert query, e.g.
const testRepository = em.getRepository(TestEntity);
testRepository.create({ tags: ['foo'] });
await testRepository.persistAndFlush();

Expected behavior Query should complete successfully. Instead, malformed array literal: "["foo"]" error will be thrown.

Additional context Add any other context about the problem here.

Versions

Dependency Version
node 14.17.0
typescript 4.3.5
mikro-orm 4.5.7
your-driver PostgreSQL

created time in 2 months

startedCyriacBr/mikro-resources

started time in 2 months

issue commentbenmosher/eslint-plugin-import

eslint-plugin-import doesn't work when load entire module

Let's put the wording aside as this is rather irrelevant here. Sorry if I confused you with it but glad you understood my example.

As for the rule itself, I don't quite understand what you mean by "can never be safely changed programmatically", but I believe this one should support any import notation — including "importing the entire module", "evaluating it for side effects" etc. There are definitely cases where you should want to use import 'something' notation, like, in my case, importing scoped CSS with babel-plugin-react-css-modules.

IlyaSavich

comment created time in 2 months

issue commentbenmosher/eslint-plugin-import

eslint-plugin-import doesn't work when load entire module

The issue describes the case with the import/order rule, when, if you import an entire module, e.g.

import '@/views/Settings/Settings.pcss';

the rule won't work compared to the case when you import a named/partial module with a from statement, e.g.

import styles from '@/views/Settings/Settings.pcss';

In this case, the import/order rule will work as expected.

IlyaSavich

comment created time in 2 months

startedcabinjs/cabin

started time in 3 months