profile
viewpoint
Dan Dascalescu dandv Ex-Google, Blueseed, Yahoo! Digital nomad https://dandascalescu.com/ Ex-@google, Yahoo!, @blueseed. Founded the Quantified Self Forum and 3 web startups.

ampproject/amp-by-example 773

DEPRECATED: AMP by Example has been merged into amp.dev

blueseed/presentation-for-startups 1

Blueseed presentation for startups, using the reveal.js framework

dandv/accounts-foursquare 0

An implementation of the Foursquare OAuth flow for Meteor

dandv/accounts-ui-bootstrap-3-with-themes 0

Display issues when comibining ian:accounts-ui-bootstrap-3 with several Bootswatch themes

dandv/acme.sh 0

A pure Unix shell script implementing ACME client protocol

dandv/activity-tracker 0

Activity Tracking App built with Meteor.

dandv/adapter 0

Shim to insulate apps from spec changes and prefix differences. Latest adapter.js release:

dandv/admin 0

Simple and powerful admin generator for meteor

dandv/agenda 0

Lightweight job scheduling for Node.js

dandv/alloy-editor 0

WYSIWYG editor based on CKEditor — with completely rewritten UI

issue openedmui-org/material-ui

Please clarify autoresize textarea

https://material-ui.com/components/text-fields/#multiline says

The multiline prop transforms the text field into a textarea or a TextareaAutosize.

It should mention when one or the other is chosen. Not hard to guess that if maxRows={4} is specified, it will return a TextArea, but what if I specify rows={4} as the initial size? Or if rows is omitted, what is the default?

Thanks!

created time in 29 minutes

issue openedgatsbyjs/gatsby

Docs: link to findpath.js is broken

At https://www.gatsbyjs.org/docs/gatsby-internals-terminology/#matchpath, the link under find-path.js is missing in the source.

But on the frontend, when resolving the page from the path (find-path.js), it is used (via reach router) to find the matching page.

created time in 2 hours

issue openedgatsbyjs/gatsby

Please clarify actions.createPage

https://www.gatsbyjs.org/docs/actions/#createPage mentions that the path parameter is "Any valid URL. Must start with a forward slash". That is incorrect - URLs must start with a non-empty scheme.

But the actual reason I've filed this issue is to get an explanation for what exactly the purpose of path is, and how it's used. The documentation could be more helpful than "must start with a forward slash".

created time in 3 hours

IssuesEvent

issue openedgatsbyjs/gatsby

Creating client-only sub-routes for static pages, /item/:id/edit

Gatsby prides itself in being not just a static site generator:

[Gatsby] allows you to make a site as feature-less or feature-rich as you want, you aren’t restricted to just static sites.

For web apps, one very common REST URL pattern is /item/:id/edit. This should be clearly documented at Hybrid app pages.

I found a similar issue #16250, but with no scalable or official solution.

created time in 4 hours

issue commentgatsbyjs/gatsby

Enable generating relative (as opposed to root-relative) URL websites

@NeliHarbuzava: considering that as well. What did you switch to?

agentofuser

comment created time in 5 hours

issue openedreact-hook-form/react-hook-form

Skip validations if a field is not required

Is your feature request related to a problem? Please describe. I have registered an optional text field with several validators. I would like to not run them at all if the field is empty.

The sandbox illustrates just one validation for simplicity.

Describe the solution you'd like If required: false, skip running the validate block.

Describe alternatives you've considered

Currently, I have to prefix each validator to return true if the input is empty.

Additional context Add any other context or screenshots about the feature request here. image

created time in 7 hours

pull request commentrclone/rclone

docs: note the sort order

A way to guarantee sorting would be useful. My use case is keeping only the N most recent backup files, named in ISO8601 format so I can sort by the filename.

Should I pipe the lsf output to sort instead?

dandv

comment created time in 9 hours

issue commentUrigo/graphql-modules

enum values not resolved to internal values

It's linked in my OP under "This GraphQL Modules CSB". Did you manage to reproduce?

dandv

comment created time in 17 hours

issue openedfacebook/jest

Lexicographic string comparison

🚀 Feature Proposal

JavaScript supports comparing strings: '2018-01-01' < '2019-01-01'. Jest should pass that through.

Motivation

I want to be able to easily compare ISO8601 dates.

Example

expect(date).toBeGreaterThan('2020-06-01')
expect(doc.updatedAt).toBeGreaterThan(doc.createdAt);

Pitch

created time in 19 hours

PR opened nginxinc/nginx-wiki

Fix link to error_log in Separating logs per host

At https://www.nginx.com/resources/wiki/start/topics/examples/separateerrorloggingpervirtualhost/, the link to error_log was broken

+1 -1

0 comment

1 changed file

pr created time in a day

push eventdandv/nginx-wiki

Dan Dascalescu

commit sha e62c0bf35f5c8b3a0f81318910c321740a67478e

Fix link to error_log in Separating logs per host

view details

push time in a day

fork dandv/nginx-wiki

Source for the wiki section of nginx.com

https://www.nginx.com/resources/wiki/

fork in a day

issue commentardatan/graphql-tools

Enum default value is not resolved to internal value

Thanks @danielrearden!

@yaacovCR: my situation was confused by using graphql-modules. I've isolated the bug to graphql-modules specifically - https://github.com/Urigo/graphql-modules/issues/1176.

ohardy

comment created time in a day

issue openedUrigo/graphql-modules

enum values not resolved to internal values

This CSB is using graphql-tools directly to echo the value of an enum. It works as expected, returning the internal values for these queries:

{
  #expect "1"
  echo(status: PENDING)
  # expect "2"
  echoDefault: echo
}

This GraphQL Modules CSB uses exactly the same code, but the typeDefs and resolvers are passed to new GraphQLModule(...) instead of makeExecutableSchema.

When running the same queries as above, the results are strings:

{
  "data": {
    "echo": "PENDING",
    "echoDefault": "APPROVED"
  }
}

Note that this is different from the older graphq-tools bug of not resolving default enum values. Even the explicitly passed PENDING value is not resolved.

created time in a day

issue openedjimkyndemeyer/js-graphql-intellij-plugin

Weird errors with an enum and graphql-modules

Describe the bug A clear and concise description of what the bug is.

To Reproduce https://github.com/dandv/js-graphql-plugin-gql-modules

  1. clone, install, npm start. Self-explanatory user.module.ts. The script runs correctly.
  2. Notice the Query' type [@14:5] tried to redefine existing 'Query' type [@13:5] error

image

If you delete the APPROVED line, the error jumps to the next line.

image

If you delete the PENDING line, the error goes away.

Undo the deletions, move all the code from user.module.ts to index.ts, the error goes away.

created time in a day

create barnchdandv/js-graphql-plugin-gql-modules

branch : master

created branch time in a day

created repositorydandv/js-graphql-plugin-gql-modules

Weird errors when using graphql-modules with the JS GraphQL plugin in WebStorm

created time in a day

issue commentardatan/graphql-tools

Enum default value is not resolved to internal value

@danielrearden: so the workaround is to pass APPROVED as the default parameter in the schema, and look up the string against my enum values in the resolver, until graphql.js fixes this?

@yaacovCR: I was using graphql-modules in production anyway, which uses graphql-tools v5 (not 6 though) and still saw the undefined error.

ohardy

comment created time in a day

issue commentgraphql/graphql-js

Enum value is not resolved to internal value for directive argumets and default values

Actually see https://github.com/ardatan/graphql-tools/issues/715#issuecomment-638532140, which shows the problem lies with graphql.js.

raduflp

comment created time in a day

issue commentardatan/graphql-tools

Enum default value is not resolved to internal value

@yaacovCR: I've updated to v6 and made the schema separately, but it seems the behavior is the same as before.

ohardy

comment created time in a day

issue commentapollographql/apollo-server

Minor version bump for graphql-tools required for GraphQL 15 compatability

I'd love it if graphql-tools were updated directly to v6 per the chore, so we can do only one major version compatibility test instead of two (v5, v6).

v6 also fixes this enum issue.

zackdotcomputer

comment created time in a day

issue commentardatan/graphql-tools

Enum default value is not resolved to internal value

I'm not sure if this is a graphql-tools issue, an apollo-graphql issue, or a graphql.js issue, but if I pass the default value in the internal representation, the resolver receives undefined.

ohardy

comment created time in a day

issue commentapollographql/apollo-server

Default enums with internal values aren't converted in input

Is it also expected that if I pass the default value to a query in the internal representation, e.g. 0, the resolver receives undefined?

FedericoBiccheddu

comment created time in a day

issue commentgraphql/graphql-js

Enum value is not resolved to internal value for directive argumets and default values

@IvanGoncharov: how do I pass the default value in the internal representation if it's a query parameter?

I've tried 0, but the resolver gets undefined. I've tried an enum value, and the resolver gets it as a string. Here's the Code Sandbox.

raduflp

comment created time in a day

issue openedtypegoose/typegoose

GitHub discussions?

Hi and thanks again for all the work on this library!

Would it be a good idea to enable the Discussions feature for this repo on GitHub? I'm thinking that new users search here when they have issues, and that might help prevent asking the same questions on Discord, which is not that searchable.

I'm suggesting this based on the good experience with Discussions since RHF enabled it, and many conversations from Spectrum moved within the project, under Discussions.

created time in 2 days

push eventdandv/typegoose

Dan Dascalescu

commit sha 5d98b1d5974da286e735e68a27646efe06c457cd

Explain the difference between ref: Class and ref: 'Class'

view details

push time in 2 days

issue commentgatsbyjs/gatsby

gatsby-node.js doesn't allow ES6 import

As an alternative, you may want to use TypeScript for gatsby-* files.

olivierpascal

comment created time in 2 days

issue commentaoi-umi/mongoose-ts

Motivation and comparison with existing modules

Because having multiple modules doing the same thing makes it harder for developers to choose the one that's not appropriate for their project.

Of course having multiple solutions is generally a good thing, as long as they're not broken subsets of others. Those are just redundant and don't help anyone.

On Tue, Jun 2, 2020, 20:27 aoi-umi notifications@github.com wrote:

i use typegoose before, and i found a bug szokodiakos/typegoose#182 https://github.com/szokodiakos/typegoose/issues/182

That's the previous version of typegoose.

Typegoose is now here: https://github.com/typegoose/typegoose

Please search before spending time creating a new package because maybe someone else has done the work and you won't have to :)

i know,but when i create the package,they had not resolved the bug. you can see my issue opened this issue on 22 Aug 2018 and they resolve at on 8 Aug 2019 and i had free time to write something, why do you care about this?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/aoi-umi/mongoose-ts/issues/1#issuecomment-637930318, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAIGINW7BH6SA2XTODAB5LRUW7IPANCNFSM4MF4TX3A .

dandv

comment created time in 2 days

startedmarkdown-it/markdown-it

started time in 2 days

PR opened mongodb/docs

See also $pull for $addToSet
+2 -1

0 comment

1 changed file

pr created time in 2 days

push eventdandv/docs

Dan Dascalescu

commit sha 7716ef3b54de6fb9964271d5df94d32c3517f3e8

See also $pull for $addToSet

view details

push time in 2 days

issue commentmui-org/material-ui

Is there a component for file input type?

There's a 3rd party MUI dropzone.

prakharrke

comment created time in 2 days

issue openedghewgill/so-static

Site dead

I realized that with a 2011 last commit, this is likely no longer maintained.

So here's the latest Wayback archive, and here's the Meta.SO question referencing it.

created time in 2 days

issue openedtypegoose/typegoose

Using transactions

I'm trying to use transactions. Are they supported?

MyModel.startSession says

TS2339: Property 'startSession' does not exist on type 'ReturnModelType '.

Versions

  • typegoose: 7
  • mongoose: 5.9.16

created time in 3 days

issue commentgatsbyjs/gatsby

Consider adding first-class support for AMP

There's also mukul-rathi/gatsby-plugin-google-amp, by @mukul-rathi. it's description indicates that the original plugin is not being maintained, as of recently.

@mukul-rathi's plugin hasn't been maintained either, and it has no Issues tab on its GitHub page.

BTW, any chance we could clean up the irrelevant "stale" bot messages from this thread, and keep only the last one? Previous ones don't really add to the conversation. Thanks.

hcavalieri

comment created time in 3 days

Pull request review commentrclone/rclone

docs: note the sort order

 There are several related list commands    * ` + "`ls`" + ` to list size and path of objects only   * ` + "`lsl`" + ` to list modification time, size and path of objects only-  * ` + "`lsd`" + ` to list directories only-  * ` + "`lsf`" + ` to list objects and directories in easy to parse format+  * ` + "`lsd`" + ` to list directories only, sorted ascending+  * ` + "`lsf`" + ` to list objects and directories in easy to parse format, sorted ascending

In my tests with 1.52, neither command recursed, so I haven't used -R or --max-depth on either. Docs say "The other list commands lsd,lsf,lsjson do not recurse by default - use "-R" to make them recurse.". I ran lsd and lsf against the root dir, where I had the files I wanted sorted, and directories to recurse into as well (but they weren't recursed into). Beyond that, I don't know :)

dandv

comment created time in 3 days

PR opened rclone/rclone

docs: note the sort order
+2 -2

0 comment

1 changed file

pr created time in 4 days

push eventdandv/rclone

Dan Dascalescu

commit sha 803e175077f4f9d358ab57ff305c156e149ec564

docs: note the sort order

view details

push time in 4 days

issue commentaoi-umi/mongoose-ts

Motivation and comparison with existing modules

i use typegoose before, and i found a bug szokodiakos/typegoose#182

That's the previous version of typegoose.

Typegoose is now here: https://github.com/typegoose/typegoose

Please search before spending time creating a new package because maybe someone else has done the work and you won't have to :)

dandv

comment created time in 4 days

issue commentschemaorg/schemaorg

Multi-line Text?

Wow thanks for the help

dandv

comment created time in 4 days

issue commentzaki-yama/typescript-npm-package-template

Comparison with existing similar packages

https://github.com/jaredpalmer/tsdx supprts UMD.

How I found your repo? By searching google for "Github typescript package". I guess you've done the same before starting yet another similar project, but didn't find anything back then?

The problem with so many packages doing the same thing, is that people have a hard time choosing among them, and each package is likely to repeat the mistakes of the previous ones.

dandv

comment created time in 4 days

issue openedairbnb/lunar

OT: Airbnb reviews collapse whitespace

@milesj @lencioni Thanks for looking into that issue I reported a while back. There's a more serious one I wish to report, after the official channels didn't work out.

The issue is that reviews are entered and displayed in sanitized HTML, but with whitespace preserved verbatim, instead of being replaced with &nbsp; and <br />s. This causes consecutive whitespace to collapse into one, rendering carefully-formatted reviews as walls of text.

Here's an example of a review where the author took time to format it intelligibly, which looks bery hard to read on the site:

image

created time in 4 days

PR opened jaredpalmer/tsdx

(docs): Comparison to -> with

Per https://english.stackexchange.com/a/588/27261

+2 -2

0 comment

1 changed file

pr created time in 4 days

push eventdandv/tsdx

Dan Dascalescu

commit sha 5d82d0b806e593523f88473b546763d9759680aa

(docs): Comparison to -> with

view details

push time in 4 days

fork dandv/tsdx

Zero-config CLI for TypeScript package development

https://npm.im/tsdx

fork in 4 days

issue openedepilande/gatsby-theme-auth0

How to prevent search engine bots from crawling .login() calls

If you submit a page on your site to Google's Rich Results Test, you may see that it failed to crawl login buttons (<Button onClick={AuthService.login}>Login</Button>.

image

How can that be prevented? These aren't links, so rel="nofollow" or robots.txt won't work.

created time in 4 days

issue commentepilande/gatsby-theme-auth0

Pass-through to Auth0

In the meantime I've been using checkSession() to renew expired JTWs, and that works. What's the difference between that and renewAuth? Would renewAuth solve the forced logout after 3 days of inactivity?

dandv

comment created time in 4 days

issue openedbeeman/template-typescript-package

Comparison with similar existing boilerplates

Hi @beeman,

Same question as here - how is this package different from the much more popular https://github.com/bitjson/typescript-starter, or the much more comprehensively documented https://github.com/chriswells0/node-typescript-template? Would help to add that to the README.

created time in 5 days

issue openedschardtbc/ts-package-template

Comparison with similar existing packages

Hi,

Same question as here - how is this package different from the much more popular https://github.com/bitjson/typescript-starter, or the much more comprehensively documented https://github.com/chriswells0/node-typescript-template? Would help to add that to the README.

created time in 5 days

issue openedzaki-yama-labs/typescript-npm-package-example

Comparison with similar existing packages

Hi,

Same question as here - how is this package different from the much more popular https://github.com/bitjson/typescript-starter, or the much more comprehensively documented https://github.com/chriswells0/node-typescript-template? Would help to add that to the README.

created time in 5 days

issue openedPedroLamas/typescript-package-template

Comparison with similar existing packages

Hi,

Same question as here - how is this package different from the much more popular https://github.com/bitjson/typescript-starter, or the much more comprehensively documented https://github.com/chriswells0/node-typescript-template? Would help to add that to the README.

created time in 5 days

issue openedzaki-yama/typescript-npm-package-template

Comparison with existing similar packages

Hi, how is this package different from the much more popular https://github.com/bitjson/typescript-starter? Would help to add that to the README/

created time in 5 days

issue openedschemaorg/schemaorg

Multi-line Text?

Is Text consisting of multiple lines supported? If so, what is the line separator? \n, I assume?

May help to specify these at https://schema.org/Text .

created time in 5 days

issue commentnfl/react-helmet

Duplicated rich snippets

Same issue here. The README clearly states "Nested or latter components will override duplicate changes", so this is an annoying bug.

Bacto

comment created time in 5 days

issue commentnfl/react-helmet

Not clear what's change from v5 to v6

Still, unanswered question, what is this "new semantic API"?

Is it by any chance

<Helmet
      meta={[
        { name: 'description', content: 'Sample' },
        { name: 'keywords', content: 'sample, something' },
      ]}
>

instead of putting <meta name="..." content="..." /> tags in <Helmet> ? I saw this used in the Gatsby default starter, but not documented in this project's README.

mlippert

comment created time in 5 days

issue closedgatsbyjs/gatsby

gatsby build => yoga-layout | nbind.js:53 | TypeError: Cannot read property 'activities' of undefined

EDIT: global gatsby-cli version 2.11.15 (perhaps related to https://github.com/gatsbyjs/gatsby/issues/23214 ?)

I can't find what is causing this error

C:\...\Roaming\npm\node_modules\gatsby-cli\node_modules\yoga-layout-prebuilt\yoga-layout\build\Release\nbind.js:53
        throw ex;
        ^

TypeError: Cannot read property 'activities' of undefined
    at getGlobalStatus (C:\...\AppData\Roaming\npm\node_modules\gatsby-cli\lib\reporter\redux\actions.js:50:54)
    at Object.createPendingActivity (C:\...\AppData\Roaming\npm\node_modules\gatsby-cli\lib\reporter\redux\actions.js:140:26)
    at Object.createPendingActivity (C:\...\AppData\Roaming\npm\node_modules\gatsby-cli\node_modules\redux\lib\redux.js:481:35)
    at prematureEnd (C:\...\AppData\Roaming\npm\node_modules\gatsby-cli\lib\reporter\index.js:89:19)
    at Object.panic (C:\...\AppData\Roaming\npm\node_modules\gatsby-cli\lib\reporter\index.js:148:5)
    at process.on.reason (C:\...\AppData\Roaming\npm\node_modules\gatsby-cli\lib\index.js:118:10)
    at process.emit (events.js:203:15)
    at processEmit (C:\...\AppData\Roaming\npm\node_modules\gatsby-cli\node_modules\signal-exit\index.js:155:32)
    at processEmit [as emit] (C:\CODING\TEST\kuworking-theme-one\node_modules\signal-exit\index.js:161:32)
    at emitPromiseRejectionWarnings (internal/process/promises.js:119:20)
    at process._tickCallback (internal/process/next_tick.js:69:34)

It can be reproduced by

git clone https://github.com/kuworking/kuworking-theme-one.git test
cd test
yarn
gatsby build
  • gatsby develop works, but when I terminate it with Ctrl+N I get the same error

  • This same repo works (both develop and build) when being within workspaces with the dependencies gatsby-theme-one, gatsby-theme-core and gatsby-theme-methods there

  • I've started (in node_modues) deleting and removing everything I could from the three packages and I've ended with I'd say nothing (only gatsby-config and package.json) and still doesn't build giving the same error message

** remaining structure after deleting as much as I've been able trying to isolate the error

kuworking-theme-one

--------------------
gatsby-config.js
--------------------
module.exports = {
  plugins: [`gatsby-theme-kuworking-one`],
};


--------------------
package.json
--------------------
{
  "name": "kuworking-theme-one",
  "version": "0.2.6",
  "description": "kuworking-theme-one",
  "author": "kuworking.com",
  "license": "MIT",
  "repository": {
    "type": "git",
    "url": "https://github.com/kuworking/kuworking-theme-one.git"
  },
  "dependencies": {
    "gatsby": "2.20.5",
    "gatsby-theme-kuworking-one": "^0.2.3",
    "react": "16.13.1",
    "react-dom": "16.13.1"
  },
  "devDependencies": {
    "babel-eslint": "10.1.0",
    "eslint": "6.8.0",
    "eslint-config-prettier": "6.10.1",
    "eslint-config-standard": "14.1.1",
    "eslint-plugin-import": "2.20.2",
    "eslint-plugin-node": "11.1.0",
    "eslint-plugin-prettier": "3.1.2",
    "eslint-plugin-promise": "4.2.1",
    "eslint-plugin-react": "7.19.0",
    "eslint-plugin-standard": "4.0.1",
    "prettier": "2.0.2"
  },
  "scripts": {
    "develop": "gatsby develop",
    "build": "gatsby build",
    "serve": "gatsby clean && gatsby build && gatsby serve",
    "net": "gatsby develop -H 192.168.1.100",
    "clean": "gatsby clean"
  }
}

gatsby-theme-kuworking-one

--------------------
gatsby-config.js
--------------------
module.exports = () => {
  return {
    plugins: [`gatsby-theme-kuworking-core`],
  }
}


--------------------
package.json
--------------------
{
  "name": "gatsby-theme-kuworking-one",
  "version": "0.2.3",
  "description": "gatsby-theme-kuworking-one",
  "main": "index.js",
  "author": "kuworking.com",
  "license": "MIT",
  "repository": {
    "type": "git",
    "url": "https://github.com/kuworking/gatsby-theme-kuworking-one.git"
  },
  "peerDependencies": {
    "gatsby": "2.20.5",
    "react": "16.13.1",
    "react-dom": "16.13.1"
  },
  "devDependencies": {
    "gatsby": "2.20.5",
    "react": "16.13.1",
    "react-dom": "16.13.1"
  },
  "dependencies": {
    "@mdx-js/react": "1.5.8",
    "gatsby-theme-kuworking-core": "^0.2.9",
    "react-cookie-consent": "3.0.0",
    "typeface-open-sans": "0.0.75"
  },
  "resolutions": {
    "**/gatsby": "2.20.5",
    "**/@emotion/core": "10.0.28",
    "**/@emotion/styled": "10.0.27",
    "**/@mdx-js/mdx": "1.5.8",
    "**/@mdx-js/react": "1.5.8",
    "theme-ui": "0.3.1"
  }
}

gatsby-theme-kuworking-core

--------------------
gatsby-config.js
--------------------
module.exports = () => {
  return {
    plugins: [
      `gatsby-transformer-sharp`,
      `gatsby-plugin-sharp`,
    ],
  }
}



--------------------
package.json
--------------------
{
  "name": "gatsby-theme-kuworking-core",
  "version": "0.2.9",
  "description": "gatsby-theme-kuworking-core",
  "main": "index.js",
  "author": "kuworking.com",
  "license": "MIT",
  "repository": {
    "type": "git",
    "url": "https://github.com/kuworking/gatsby-theme-kuworking-core.git"
  },
  "peerDependencies": {
    "@mdx-js/react": "1.5.8",
    "gatsby": "2.20.5",
    "react": "16.13.1",
    "react-dom": "16.13.1"
  },
  "devDependencies": {
    "@mdx-js/react": "1.5.8",
    "gatsby": "2.20.5",
    "react": "16.13.1",
    "react-dom": "16.13.1"
  },
  "dependencies": {
    "@emotion/core": "10.0.28",
    "@emotion/styled": "10.0.27",
    "@mdx-js/mdx": "1.5.8",
    "@mdx-js/react": "1.5.8",
    "emotion-icons": "1.0.0",
    "gatsby-image": "2.3.1",
    "gatsby-plugin-emotion": "4.2.1",
    "gatsby-plugin-feed": "2.4.1",
    "gatsby-plugin-google-tagmanager": "2.2.1",
    "gatsby-plugin-manifest": "2.3.3",
    "gatsby-plugin-mdx": "1.1.6",
    "gatsby-plugin-offline": "3.1.2",
    "gatsby-plugin-page-creator": "2.2.1",
    "gatsby-plugin-react-helmet": "3.2.4",
    "gatsby-plugin-robots-txt": "1.5.0",
    "gatsby-plugin-sharp": "2.5.3",
    "gatsby-plugin-sitemap": "2.3.1",
    "gatsby-plugin-theme-ui": "0.3.0",
    "gatsby-remark-copy-linked-files": "2.2.1",
    "gatsby-remark-images": "3.2.1",
    "gatsby-source-filesystem": "2.2.2",
    "gatsby-theme-kuworking-methods": "^0.1.15",
    "gatsby-transformer-sharp": "2.4.3",
    "react-helmet": "6.0.0",
    "remark-slug": "6.0.0",
    "theme-ui": "0.3.1"
  },
  "resolutions": {
    "**/gatsby": "2.20.5",
    "**/@emotion/core": "10.0.28",
    "**/@emotion/styled": "10.0.27",
    "**/@mdx-js/mdx": "1.5.8",
    "**/@mdx-js/react": "1.5.8",
    "theme-ui": "0.3.1"
  },
  "scripts": {
    "develop": "gatsby develop",
    "build": "gatsby build",
    "serve": "gatsby clean && gatsby build && gatsby serve",
    "net": "gatsby develop -H 192.168.1.100",
    "clean": "gatsby clean",
    "bump": "."
  }
}

closed time in 5 days

kuworking
IssuesEvent

issue commentgatsbyjs/gatsby

TypeScript sites break with gatsby@2.9.9

I'm on Gatsby 2.22.13 and get this cryptic error,

/sandbox/node_modules/yoga-layout-prebuilt/yoga-layout/build/Release/nbind.js:53
        throw ex;
        ^

Error: write EPIPE

Here's the Code Sandbox.

ryanditjia

comment created time in 5 days

IssuesEvent

issue commentgatsbyjs/gatsby

gatsby build => yoga-layout | nbind.js:53 | TypeError: Cannot read property 'activities' of undefined

I'm on Gatsby 2.22.13 and get this cryptic error,

/sandbox/node_modules/yoga-layout-prebuilt/yoga-layout/build/Release/nbind.js:53
        throw ex;
        ^

Error: write EPIPE

Here's the Code Sandbox.

kuworking

comment created time in 5 days

issue commentfacebook/react

TypeError: Object(...) is not a function

All these comments about how tiny typos caused all this time waste and frustration, suggest that this error could be clarified by echoing the incorrect name. @gaearon, anything that could be done in that direction, or is this a JavaScript limitation?

sagar-gavhane

comment created time in 5 days

PR opened gatsbyjs/gatsby

docs: the location prop is only passed to page components

Description

Clarify when the location prop is automatically passed to components.

Documentation

https://www.gatsbyjs.org/docs/location-data-from-props/

Demo

Related Issues

Related to #8787

+1 -1

0 comment

1 changed file

pr created time in 5 days

create barnchgatsbyjs/gatsby

branch : dandv-location-page

created branch time in 5 days

issue commentsmartlook/smartlook-client

"API is not enabled in project settings" warning in the console

I can't check the EU API box during the free trial. So if that's blocking California visitors, I can't really evaluate the product.

dandv

comment created time in 5 days

issue commentmui-org/material-ui

docs: pros & cons for dynamic variations when customizing

new users would pick the first one (no need for pros/cons)

I'm a new user who likes to make informed choices. I never just pick the first option without understanding why. Maybe if I didn't care, and the docs said something like "in most cases you'll want to go with #1", then yes. But otherwise, with just a list of options and no guidance, how would I distinguish a list of 5 equally good options, from a list of 5 where the first is much better in most situations?

dandv

comment created time in 5 days

issue commentgatsbyjs/gatsby

How can I get the current url (or path) in a page in v2

@jlengstorf: thanks for that example! To clarify, location is passed to the SecondPage component by the Gatsby Link component in the to attribute.

PS: page-2.js has an unused import { Location } from '@reach/router'.

amingilani

comment created time in 6 days

PR opened gatsbyjs/gatsby

docs: explain exactly how to add JSON+LD data

Adding JSON+LD data in a script tag with react-helmet is non-trivial, and there are long threads about the pitfalls.

This PR adds basic usage of the <Helmet> tag.

+15 -13

0 comment

1 changed file

pr created time in 6 days

create barnchgatsbyjs/gatsby

branch : dandv-json-ld

created branch time in 6 days

issue commentnpm/rfcs

[RRFC] Deprecated packages: automatically display dependents, to ease notifying maintainers

I'd be happy to see that in v7 as well. Should I file the issue somewhere else (it can also be moved to a different GitHub repo by an org owner, but no problem to file it again in the cli repo for instance).

As for popular deprecations, the noise should incentivize solutions :)

dandv

comment created time in 6 days

issue commentSparkPost/node-sparkpost

npm request deprecated. please update. thanks.

There's no good reason to stick with the bloated request. See #252.

Has anyone from the @sstaley-sparkpost team seen the request issues?

lvnilesh

comment created time in 6 days

issue openedgatsbyjs/gatsby

@babel/polyfill has been deprecated

Summary

Installing gatsby produces a number of npm warnings about deprecated packages. While hunting down one of them, I noticed that gatsby depends on @babel/polyfill, which has been deprecated.

In turn, @babel/polyfill depends on core-js@2, which has been deprecated and generates this warning when installing any Gatsby project:

$ npm install
npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.

Motivation

Many users are confused by NPM warnings about deprecated packages:

created time in 6 days

issue commentmui-org/material-ui

Popper changed home

This prompted me to file a feature request for npm to automatically show what package(s) depend on the deprecated one.

RDIL

comment created time in 6 days

issue openednpm/rfcs

[RRFC] Deprecated packages: automatically display dependents, to ease notifying maintainers

<!--

Before Opening Please...

  • [x] Search for an existing/duplicate RRFC which might be relevant to your RRFC -->

Motivation ("The Why")

Very often when users install a package, they see warnings about deprecated dependencies, and don't know what to do about them.

Example

Here are some examples from StackOverflow of user confused by this:

How

Current Behaviour

image

Desired Behaviour

npm could automatically integrate the output of npm ls <deprecated-package:

$ npm install
npm WARN deprecated popper.js@1.16.1: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
└─┬ @material-ui/core@4.10.0
  └── popper.js@1.16.1 

created time in 6 days

issue commentgatsbyjs/gatsby

Can't perform a React state update on an unmounted component. When adding useeffect on navigation component

I'm getting the same error, without useEffect (only useState), and only in Gatsby development mode; not from the statically built and deployed pages.

faizhameed

comment created time in 7 days

issue commentgatsbyjs/gatsby

Dynamic route (/product/id) with static layout

@slorber: as I was reading this in your old post,

Then, your component will need to extract the path param from the url (as it's not provided by Gatsby, see #13965)

I went to that issue and spent time figuring out what the problem was. That's just not necessary any more, so I was suggesting editing that old post, so that others who land here won't waste time looking into that resolved issue.

Anyway, thanks for the solution in the other thread!

slorber

comment created time in 7 days

issue commentgatsbyjs/gatsby

Gatsby clientside pages: inject route match params as props

That worked, thanks. For the dynamic route, I noticed that it doesn't matter when you pass in the path after /bookings (:WHATEVER worked), so I left it at path: '/bookings'.

slorber

comment created time in 7 days

issue openedsmartlook/smartlook-client

Client blocked by ad blockers

Unsurprisingly, the recorder script is blocked by ad blockers.

image

Would it be possible to actually include the code in this package (instead of it being a thin wrapper over the script), in order to avoid that problem?

created time in 7 days

issue commentsmartlook/smartlook-client

"API is not enabled in project settings" warning in the console

Yes, the visitor was from California. Do I need to check the EU switch? Or should there be a 3rd switch for California?

image

dandv

comment created time in 7 days

issue openedjimkyndemeyer/js-graphql-intellij-plugin

The parent selection or operation does not resolve to a valid schema type

Before you create the issue

  • [x] Please search the existing issues at https://github.com/jimkyndemeyer/js-graphql-intellij-plugin/issues?q=sort%3Aupdated-desc before opening a new issue.
  • [ ] Read the FAQ at https://github.com/jimkyndemeyer/js-graphql-intellij-plugin#faq - no FAQ there

Version and Environment Details

Operation system: Ubuntu 20

IDE name and version: WebStorm 2020.2 EAP, Build #WS-202.4357.21, built on May 26, 2020

Plugin version: 2.4.0

Steps to Reproduce / Link to Repo with Reproduction and Instructions

I use graphql-modules on the server, and in my web app I have a .tsx file with this query

gql`
    query($id: ID!) {
      product(id: $ID) {
        id
      }
    }
  `

On the server, the schema looks like this:

export const ProductModule = new GraphQLModule({
  imports: [
    AuthModule,
  ],

  typeDefs: gql`
    scalar DateTime

    input ProductInput {
      ...
    }

    "Alias: Item"
    type Product {
      id: ID!
      "Alias: title"
      name: String!
      ...
    }

    type Query {
      "Find product by id"
      product(id: ID!): Product
      ...
    }

I can work on a reproduction repo upon request.

created time in 7 days

issue openedjimkyndemeyer/js-graphql-intellij-plugin

Issues with the GitHub issue template

  1. https://github.com/jimkyndemeyer/js-graphql-intellij-plugin/blob/master/.github/ISSUE_TEMPLATE.md shows a warning about using an old version of the issues template

  2. The link to the FAQ doesn't lead anywhere - was this removed from the README?

created time in 7 days

issue commentjimkyndemeyer/js-graphql-intellij-plugin

Cursor lands at weird position after pressing Enter

Any updates on this?

dandv

comment created time in 7 days

issue commentsmartlook/smartlook-client

"API is not enabled in project settings" warning in the console

That was enabled by default already for non-EU. My user is from the US.

On Thu, May 28, 2020, 04:35 David Kadlec notifications@github.com wrote:

Hi @dandv https://github.com/dandv

You need to enable API in project settings.

[image: image] https://user-images.githubusercontent.com/2790687/83136540-2b1daf80-a0d7-11ea-987d-8bf9a24f1ee2.png

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/smartlook/smartlook-client/issues/9#issuecomment-635285188, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAIGIONDOTTVLCRY2FLA2TRTZD6ZANCNFSM4NM75AFA .

dandv

comment created time in 8 days

issue openedsmartlook/smartlook-client

"API is not enabled in project settings" warning in the console

I see this after initializing the client. Recording works (minus the layout being wonky).

What does the warning mean? I can't find anything in the help.

created time in 8 days

push eventdandv/smartlook.github.io

Dan Dascalescu

commit sha cc0d30f7ac0f568ca9a0dd6e4ace75042d17432c

Improve English for identify

view details

push time in 8 days

issue openedsmartlook/smartlook-client

FR: add basic support for logging from Node

Just being able to log custom errors from server-side code, would mostly eliminate the need for using a separate error tracking service for the backend.

No need for recording, obviously. Just .error and .identify.

created time in 8 days

issue openedsmartlook/smartlook-client

Confusing call convention

In the README here, the calling convention is smartlookClientmethod, for example smartlookClient.identify(12345, { ... }).

At the bottom, the README links to the docs site.

There, the calling convention is smartlookClient('method', ...args). For example, smartlook('identify', user_id);.

created time in 8 days

push eventdandv/smartlook-client

Dan Dascalescu

commit sha 41ea4d1c09a10533735e6e5a318b08235afe495d

Add syntax highlight to the code sample

view details

push time in 8 days

fork dandv/smartlook-client

Official Smartlook client for easy frontend integration.

https://smartlook.com

fork in 8 days

push eventdandv/comparisons

Dan Dascalescu

commit sha d8c4e425dd403b507dee64acdc722af290f8d855

Delete js-error-monitoring.md

view details

push time in 8 days

issue commentgatsbyjs/gatsby

Gatsby clientside pages: inject route match params as props

@brisa-pedronetto's example generates one static page in gatsby-node, then the React component renders it.

Is it possible to generate multiple static pages for existing bookingIds, and render newly created ones dynamically, with the same template? The use case is items that get created rarely, but accessed frequently, so SSR would help. However, when an admin creates an item, it should be rendered right away, rather than waiting for Gatsby to rebuild.

I have the equivalent of,

for (const booking of bookings)
  actions.createPage({
    path: `/bookings/${booking.id}`,
    component: resolve('./src/templates/booking.tsx'),
    context: {
      booking,
    },
//    matchPath: '/bookings/:id',
  });

which generates pages for the existing bookings via booking.tsx (which takes the booking via pageContext). But if I uncomment the matchPath, then Gatsby only generates one static page, the first one. If I change the path line to path: '/bookings/:id', it generates only one static page, for the last booking in the array.

slorber

comment created time in 8 days

issue commentvalidatorjs/validator.js

Could not find a declaration file for module with TypeScript

Related: #1204. Wish I had time to volunteer to convert this project to TypeScript.

steida

comment created time in 8 days

issue commentgatsbyjs/gatsby

Dynamic route (/product/id) with static layout

@slorber: can you please update your earlier post now that Gatsby behaves as expected?

slorber

comment created time in 8 days

issue openedfireflysemantics/validatorts

Credit the original package, add usage etc.

I'm happy to see someone took initiative to just get the TypeScript rewrite done when it was "out of the question" for the original project.

But seeing that this rewrite has had no traction so far, is not encouraging.

Some ideas:

  1. Credit the original package in the README.
  2. Add some documentation.

created time in 8 days

startedfireflysemantics/validatorts

started time in 8 days

issue commentvalidatorjs/validator.js

[Question] How can we better support TypeScript?

From an end-user's perspective, I don't see why "a TS rewrite is out of the question". I realize that from the developers' perspective that might well be the case, but as a user, I just want a clean TypeScript source that I can import without all the shenanigans like #1208, #1204, #1015 etc. It's 2020 after all.

fireflysemantics

comment created time in 8 days

more