Deleting
.buildthen runningsls deployworked for me
Came back months later when upgrading to runtime: nodejs14.x for optional chaining. The above worked again 👍
Pinned
D-Pagey/pagey.dev
0
⚡ Old personal website
Activity
Nov
2
4 weeks ago
D-Pagey issue comment serverless/serverless-plugin-typescript
D-Pagey
Oct
8
1 month ago
D-Pagey issue comment remix-run/react-router
D-Pagey
[Bug]: history.push results in empty search value
What version of React Router are you using?
5.3.0
Steps to Reproduce
- Navigate to any route with a query param in the url
- User click to navigate to a different url with a query parameter
history.push(`www.example.com/some/route?target=${uuid}`)
- The location.search field will be empty in the route despite being in the url
Expected Behavior
The search field should be populated with ?target=dad... and not empty
Actual Behavior
The search field is empty
D-Pagey
I don't understand why the search value would be empty when the pathname shows the query param. I couldn't find an explanation in the docs either.
D-Pagey issue remix-run/react-router
D-Pagey
[Bug]: history.push results in empty search value
What version of React Router are you using?
5.3.0
Steps to Reproduce
- Navigate to any route with a query param in the url
- User click to navigate to a different url with a query parameter
history.push(`www.example.com/some/route?target=${uuid}`)
- The location.search field will be empty in the route despite being in the url
Expected Behavior
The search field should be populated with ?target=dad... and not empty
Actual Behavior
The search field is empty
Sep
22
2 months ago
Sep
13
2 months ago
Sep
9
2 months ago
D-Pagey push D-Pagey/pagey.dev
D-Pagey
Update README.md
commit sha： 14208de9e69f0062eabdd575d97f59ed0c32f92e
push time in 2 months ago
Error EPERM: operation not permitted, version 1.1.9
When I tried to run 'sls deploy', following error is shown:
EPERM: operation not permitted, unlink '/Users/sofyan.ahmad/Projects/zenius/zenius-membership/services/influencer/.build/node_modules'The error is gone when I reverted back to version 1.1.7