smooth-dnd | drag and drop library for javascript | Widget library
kandi X-RAY | smooth-dnd Summary
kandi X-RAY | smooth-dnd Summary
drag and drop library for javascript
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of smooth-dnd
smooth-dnd Key Features
smooth-dnd Examples and Code Snippets
Community Discussions
Trending Discussions on smooth-dnd
QUESTION
The app has been running successfully in production for a year, and works perfectly on MacOS localhost. Recently needed to set up the app to run on Windows 10 localhost, and after resolving all the errors, now the app boots up, requests seem to get through, however, only the '/' page actually renders, all the other routes don't render and stay at a blank page.
What could be a reason?
During initial setup, I ran into an issue with windows-build-tools and a missing Python, which I ended up eventually resolving by installing everything through Chocolatey. Could this be related?
Node version on Windows is newer than one specified in project, could this cause this?
I'm happy to provide more details and perform any experiments any of you recommend or suggest. My own guess is that it is either something related to setup on Windows or some issue with the packages on Windows.
The app is booted up through a package.json
start script:
ANSWER
Answered 2021-Dec-14 at 19:01Node version could be a problem. That windows-build-tools is required for the installation indicates there's binary dependency that is potentially incompatible with current Node version. Binary NPM dependencies usually provide a subset of precompiled binaries for a specific package version, where a combination of platform and Node.js version that can be considered safe or supported. For any other combination, binary package needs to be compiled for current platform with build tools. This doesn't always mean that the package is incompatible but this is common.
For example, node-sass
(doesn't seem to be used here) has different versions that correspond to specific Node.js versions and provides precompiled binaries for a supported subset; for unsupported Node.js version it falls back to compilation during installation process and most likely fails.
It's unknown which dependency causes this problem in this case, this needs to be reviewed in npm/yarn logs.
In order to avoid this situation, Node version could be matched with old one. Project dependencies need to be freshly installed because node_modules in use has been already tied to currently used Node version.
QUESTION
Until starting up my computer this morning the following worked:
...ANSWER
Answered 2020-Jan-05 at 09:00Probably ignore-scripts=true
was set in .npmrc
Run: npm config set ignore-scripts false
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install smooth-dnd
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page